Details
-
Improvement
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
Description
Problem
Some config properties that reside either in a file or in an external system (db) may change over time. We need a mechanism to reload and reapply the new configuration without a redeploy.
Developer notes
- Implementing support for Provider<Property> has a limited use case, as some of the services are expensive to initialise. For these cases, a callback/hook mechanism might be required.
- Consider using Tomcat management/JMX beans to communicate the config update events and use annotated interfaces that core process could trigger an update for.
Example configs
- SSO
- Publication
- Caching
Checklists
Acceptance criteria