It's not clear to me what is not actually straightforward about managing a
text configuration file.
In any case, just about every platform and architecture has a way to manage
configuration files. Helm charts are a good example. One of the goals with
keeping the "create" command simple is so that
Hi Justin,
Yes, I could have done that but I wanted to know if there are straight
forward ways of doing such things. Just for the sake of other/future users,
I found an approach of achieving this in a project on github
https://deviceinsight.github.io/activemq-artemis-helm
Although, I wont be
The "create" command only supports a handful of customizable configuration
options. It is meant to be a simple tool to perform simple customizations.
For more advanced use-cases you simply need to provide your own broker.xml.
I recommend you use the "create" command to create a default broker.xml
Hi All,
My requirement is to start/create a new broker with custom settings which
are specified in the broker.xml file. These settings include things like,
1. Specifying/adding new queues and topics.
2. Specifying custom broadcast settings like jgroups settings
5000
* test