Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POLIO-1722 add endpoint to refresh OpenHexa VRF data #1963

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

quang-le
Copy link
Member

PowerBi can't refresh data handled by OpenHexa pipelines so we need an endpoint in iaso to handle that

Related JIRA tickets : IA-XXX, WC2-XXX, POLIO-1722

Self proofreading checklist

  • Did I use eslint and black formatters
  • Is my code clear enough and well documented
  • [] Are my typescript files well typed
  • New translations have been added or updated if new strings have been introduced in the frontend
  • My migrations file are included
  • Are there enough tests
  • Documentation has been included (for new feature)

Doc

NA

Changes

  • Add an endpoint using ExternalTaskViewset
  • Override list method to behave like POST, because powerBI can't POST

How to test

  • Login to OpenHexa's polio workspace
  • Deploy the branch on staging
  • go to api/polio/tasks/refreshvrf/:
    • A new task should be visible in the tasks list
    • In openHexa, the pipeline should have run, with the task id ans "staging" as parameters
    • in OpenHExa, the DB table VaccineRequestFormsStaging should have been updated

Print screen / video

Screenshot 2025-02-10 at 12 31 28

Notes

Once the PR is merged, there are additional steps to perform to switch to prod:

  • Update the powerBI dashboard so that the refresh button attacks the new API. Make a copy of the dashbaord that points to staging data first
  • Then:
    • Add the vrf-pipeline-configto prod. It can be copied from staging, with just thetarget` adpated.
    • Update the prod dashboard
    • Delete the old Jupyter notebook, since the code now lives on github

Follow the Conventional Commits specification

The merge message of a pull request must follow the Conventional Commits specification.

This convention helps to automatically generate release notes.

Use lowercase for consistency.

Example:

fix: empty instance pop up

Refs: IA-3665

Note that the Jira reference is preceded by a line break.

Both the line break and the Jira reference are entered in the Add an optional extended description… field.

@quang-le quang-le changed the title POLIO-1722 add endpoint to refresh OpneHexa VRF data POLIO-1722 add endpoint to refresh OpenHexa VRF data Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants