[MAGNOLIA-8089] Implement JMX-based handle for project configuration refreshing Created: 10/May/21  Updated: 13/May/22  Resolved: 27/May/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0

Type: New Feature Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Andrei Ichimescu
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Epic Link: SaaS project configuration
Sprint: Cloud Service 8, Cloud Service 9, Cloud Service 10
Story Points: 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.

Generated at Mon Feb 12 04:29:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.