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

patch temporary fix to address WF2 error unexpected relative url #86

Merged
merged 1 commit into from
Jan 17, 2025

Conversation

aleksa-krolls
Copy link
Collaborator

@aleksa-krolls aleksa-krolls commented Jan 16, 2025

Patch to run_msf_addons.sh to address issue Joshua was facing when testing WF2 Get Encounters step. This step uses http adaptor because we query the OMRS FHIR api, which requires baseUrl in the auth configuration... but the omrs adaptor (used in the other workflow steps) uses instanceUrl. In the immediate term, Josh addressed this by manually adding a new credential with baseUrl to the WF2 in his deployed instance.

Merge this change if you want to ensure deployment of this project.yaml will work instantly, without manual intervention.

Otherwise next week (estimated date: Jan 22), there will be an openmrs adaptor release with an enhancement that we can leverage and apply to the project.yaml file so that all OMRS workflow steps can use the openmrs adaptor. If no rush, then you can wait until this upcoming change next week, and not yet merge this PR. Be in touch!

Related Issue

See slack msg where Joshua flagged Get Encounters step in WF2 fails with error UNEXPECTED_RELATIVE_URL

Patch to `run_msf_addons.sh` to address issue Josh was facing when testing WF2 `Get Encounters` step. This step uses `http` adaptor because we query the OMRS FHIR api, which requires `baseUrl` in the auth configuration... but the `omrs` adaptor (used in the other workflow steps) uses `instanceUrl`. In the immediate term, Josh addressed this by manually adding a new credential with `baseUrl` to the WF2 in his deployed instance. 

Merge this change if you want to ensure deployment of this `project.yaml` will work instantly, without manual intervention. 

Otherwise next week (estimated date: Jan 22), there will be an `openmrs` adaptor release with an enhancement that we can leverage and apply to the `project.yaml` file so that _all_ OMRS workflow steps can use the `openmrs` adaptor. If no rush, then you can wait until this upcoming change, and not merge this PR.
Copy link
Collaborator

@jnsereko jnsereko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @aleksa-krolls

@jnsereko jnsereko merged commit eaef1db into MSF-OCG:main Jan 17, 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