Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.25.0
-
None
Description
Following on from ARTEMIS-4001 - in kubernetties - where properties can be mounted as projections of config maps, there can be a large delay between update and the refresh being visible to the broker.
Adding a status attribute to the server control that is driven by configuration, will allow properties files to embed version or status information and see those reflected via admin or jolokia queries.
This then provides a nice feedback loop. I am calling it status like MetaData status, but also leaving it free form such that any sensible json can be embedded once there is coordination.
Initially the value will just be set like any property.
Eventually it could provide an entry point for the parser to inform of property key=value mismatch or errors on update in some "error" section.
Attachments
Issue Links
- relates to
-
ARTEMIS-4025 properties config - provide error status for invalid properties
- Closed
-
ARTEMIS-4028 properties config - provide checksum read status for properties
- Closed
- links to