-
Notifications
You must be signed in to change notification settings - Fork 3
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
Enhancement to support validation via CI #305
Comments
Did some investigating, this is the block of code that does the the server POST request - https://github.com/onaio/fhir-tooling/blob/main/efsity/src/main/java/org/smartregister/command/QuestionnaireResponseGeneratorCommand.java#L182-L185 Do we need to perform a server submission when doing validation? |
Hey @ndegwamartin, yes we do The idea for CI was to just have a job that starts up the FHIR server which can be used for the process. An alternative would be to deploy a server just for this that the CI can connect to... depending on whichever makes more sense |
Got it. So then yeah I think we need to reach out to SRE on this so that they can provision a validation server. Perhaps generically it should be an OpenSRP Terminology server that we can use to also provide our custom ones cc @dubdabasoduba @pld |
This issue is blocked by - #306 . It will be fixed by updating the hardcoded URL of the validation server to the new host after deployment. |
No longer necessary since https://github.com/onaio/fhir-resources/pull/3589 was already closed |
A follow up task to issue #199 based on the comment here #281 (comment)
As part of validation efsity tries to connect to the FHIR Base URL server defined for the
QuestionnaireResponse
generated here for validation - https://github.com/onaio/fhir-tooling/blob/199-validate-sm/efsity/src/main/java/org/smartregister/command/ValidateStructureMapCommand.java#L106-L115 leading to the exception here :This can be reproduced by running the structure map validation command e.g. via command line to validate.
The text was updated successfully, but these errors were encountered: