Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

Add Mechanism to Communicate Process Deployment State Back to Process Plugin #261

Closed
hhund opened this issue Sep 2, 2021 · 1 comment · Fixed by #291 or #347
Closed

Add Mechanism to Communicate Process Deployment State Back to Process Plugin #261

hhund opened this issue Sep 2, 2021 · 1 comment · Fixed by #291 or #347
Assignees
Labels
enhancement New feature or request ready for release Issue is fixed and merged into develop, ready for next release
Milestone

Comments

@hhund
Copy link
Member

hhund commented Sep 2, 2021

We should add a mechanism to communicate the process deployment state (active, suspended) back to the process plugin. This mechanism could be used to perform for example connection tests to external servers only if a process that requires the connection is actually active.

For example the DataTranslate process from https://github.com/num-codex/codex-processes-ap1 does not require a connection test to the local GECKO FHIR server.

@hhund hhund added the enhancement New feature or request label Sep 2, 2021
@hhund
Copy link
Member Author

hhund commented Sep 2, 2021

#262 might solve this issue as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request ready for release Issue is fixed and merged into develop, ready for next release
Projects
None yet
1 participant