Once
is merged, then when the beamline parameters or other config is altered, in order for hyperion-blueapi to pick up the new settings, we will need to reload the blueapi context.
This means that hyperion-supervisor will need to trigger a reload of the blueapi context - on baton handover to hyperion, we should delete the current environment with a REST call to hyperion-blueapi in order to flush the cached blueapi context.
We will also need some mechanism whereby the config server cache can be reloaded
No need to reset the config-server cache in blueapi mode as deleting the environment terminates the process containing the blueapi context
Acceptance Criteria
hyperion-blueapi picks up new config when hyperion is handed the baton
Once
is merged, then when the beamline parameters or other config is altered, in order for
hyperion-blueapito pick up the new settings, we will need to reload the blueapi context.This means that
hyperion-supervisorwill need to trigger a reload of the blueapi context - on baton handover to hyperion, we should delete the current environment with a REST call tohyperion-blueapiin order to flush the cached blueapi context.We will also need some mechanism whereby the config server cache can be reloadedNo need to reset the config-server cache in blueapi mode as deleting the environment terminates the process containing the blueapi context
Acceptance Criteria
hyperion-blueapipicks up new config when hyperion is handed the baton