Gary Tully created ARTEMIS-4007:
-----------------------------------
Summary: properties config - complete feedback loop with server
status attribute
Key: ARTEMIS-4007
URL: https://issues.apache.org/jira/browse/ARTEMIS-4007
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Configuration
Affects Versions: 2.25.0
Reporter: Gary Tully
Assignee: Gary Tully
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 is provides a nice feedback loop. I am calling it status like CR status,
but also leaving it free from 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
