[
https://issues.apache.org/jira/browse/ARTEMIS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated ARTEMIS-4007:
--------------------------------
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|https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#:~:text=The%20status%20describes%20the%20current,the%20desired%20state%20you%20supplied],
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.
was:
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.
> 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
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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|https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#:~:text=The%20status%20describes%20the%20current,the%20desired%20state%20you%20supplied],
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
