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 we don't waste time solving a problem that already has a solution. There's lots of ways to manage simple text configuration files. You just need to find the right one for your specific use-case. Justin On Mon, Mar 27, 2023 at 9:37 AM prateekjai...@gmail.com < prateekjai...@gmail.com> wrote: > 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 using it as-it-is but yes, it does answer most of my > questions. > > Regards, > Prateek Jain > > -------------------------------------------------------------- > EXPECTATION : Causes all troubles...... > -------------------------------------------------------------- > > > On Mon, Mar 27, 2023 at 3:22 PM Justin Bertram <jbert...@apache.org> > wrote: > > > 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 > and > > then modify it as needed. Then you can save that and copy it to any > > instance you need. It should be really straightforward. > > > > > > Justin > > > > On Mon, Mar 27, 2023 at 7:02 AM prateekjai...@gmail.com < > > prateekjai...@gmail.com> wrote: > > > > > 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 > > > > > > <broadcast-groups> > > > <broadcast-group name="bg-group1"> > > > <broadcast-period>5000</broadcast-period> > > > > > > * <jgroups-file>test-jgroups_ping.xml</jgroups-file> > > > <jgroups-channel>active_broadcast_channel</jgroups-channel>* > > > <connector-ref>artemis</connector-ref> > > > </broadcast-group> > > > </broadcast-groups> > > > > > > 3. Specifying address settings like, > > > <redistribution-delay>0</redistribution-delay> > > > > > > I saw some threads like > > > > > > > > > https://stackoverflow.com/questions/71149959/how-to-provide-a-custom-broker-xml-to-activemq-artemis-broker-instance > > > > > > But answer provided doesn't run. > > > > > > Any clues, how this can be achieved? Any command line flags that can be > > > used to achieve the same, for example I found this, > > > > > > ./artemis create test-broker-01 \ > > > --http-host $HOSTNAME \ > > > --host $HOSTNAME \ > > > --aio \ > > > --clustered \ > > > --cluster-user administrator \ > > > --cluster-password TestPassw0rd \ > > > --name live-broker-01 \ > > > --max-hops 1 \ > > > --user administrator \ > > > --password TestPassw0rd \ > > > --require-login \ > > > --port-offset 0 \ > > > --no-autocreate \ > > > --data /usr/shared/artemis-data/$HOSTNAME \ > > > --shared-store \ > > > --failover-on-shutdown > > > > > > > > > Regards, > > > > > > Prateek Jain > > > -------------------------------------------------------------- > > > EXPECTATION : Causes all troubles...... > > > -------------------------------------------------------------- > > > > > >
