You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2025/02/26 17:54:00 UTC
[jira] [Updated] (ARTEMIS-5332) add exportConfigAsProperties operation to server control
[ https://issues.apache.org/jira/browse/ARTEMIS-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully updated ARTEMIS-5332:
--------------------------------
Summary: add exportConfigAsProperties operation to server control (was: add exportConfigAsPropertes operation to server control)
> add exportConfigAsProperties operation to server control
> --------------------------------------------------------
>
> Key: ARTEMIS-5332
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5332
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Configuration, management
> Affects Versions: 2.39.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
>
> With broker properties, it is non trivial to figure out the syntax as it reflects the internal structure of the broker configuration bean and its composites.
> having a way to see the effective config, with all default values in play would be useful even with just xml config.
> The broker sets java.io.tmpdir to instance/tmp when it is unset, we can write a file there with the current broker config in properties format. That should be writable, if not, the operation fail.
> we can use the existing rbac to control access to this operation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact