It is a fairly common use case to reload the configuration from the git repository, or from a local location during the configuration of the API portal.
Currently, reloading the configuration usually means redeploying/manually restarting the entire deployment, which is not strictly necessary.
Usually, it is enough to trigger a reload of the API component, which in turn will trigger a reload of all the other components. This happens because an internal "hash" of the configuration is calculated, and this changes if the configuration changes.
On the System Health page, visible only to Admins, there should be a "Reload Configuration" button, which triggers a restart of the API component, and also restarts the other components, either forced, or after the reload of the configuration (this would happen anyway).
It is a fairly common use case to reload the configuration from the git repository, or from a local location during the configuration of the API portal.
Currently, reloading the configuration usually means redeploying/manually restarting the entire deployment, which is not strictly necessary.
Usually, it is enough to trigger a reload of the API component, which in turn will trigger a reload of all the other components. This happens because an internal "hash" of the configuration is calculated, and this changes if the configuration changes.
On the System Health page, visible only to Admins, there should be a "Reload Configuration" button, which triggers a restart of the API component, and also restarts the other components, either forced, or after the reload of the configuration (this would happen anyway).