Details
-
New Feature
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Cloud Service 8, Cloud Service 9, Cloud Service 10
-
8
Description
For rest/s3-based cfg source we can't provide Magnolia-native change observation solution (esp for S3 where we need to subscribe to SNS/SQS with all the quirks), we could externalise observation into own service, while letting Magnolia be pinged merely over JMX.
AC:
- add POST-consuming endpoint to the vitals webapp, wait for the changed resources to be communicated from the observation service
- add/register JMX operation within core Magnolia
- trigger the operation upon update
- can use YamlConfigurationSource as a test bed before the S3 one lands.
Checklists
Acceptance criteria