You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For any FHIR servers determined to not be prod-available in the QC by default, remove these servers from the flyway migrations and instead place them into a DIBBs custom asset JSON file, just as we did with our queries, valuesets, and the like. There should just be a simple structure you should need to define and then parse during app startup to populate the fhir-servers const array with the information we load from this file. Note that this will need to happen automatically on `docker compose up` so that connections are in place for any seeding operations.
Acceptance Criteria:
Non-prod fhir servers are removed from DB startup
The text was updated successfully, but these errors were encountered:
Description:
For any FHIR servers determined to not be prod-available in the QC by default, remove these servers from the flyway migrations and instead place them into a DIBBs custom asset JSON file, just as we did with our queries, valuesets, and the like. There should just be a simple structure you should need to define and then parse during app startup to populate the fhir-servers const array with the information we load from this file. Note that this will need to happen automatically on `docker compose up` so that connections are in place for any seeding operations.
Acceptance Criteria:
Non-prod fhir servers are removed from DB startup
The text was updated successfully, but these errors were encountered: