[rabbitmq-discuss] rabbitmqadmin and default node behaviour
Simon MacMullen
simon at rabbitmq.com
Tue Oct 30 10:53:35 GMT 2012
On 29/10/12 16:04, Simon Lundström wrote:
> So, my new suggestion is:
>
> Parse the config/defaults in this order:
> # defaults from default_options hash^Wdictionary
> # config file, one of:
> ## specified via --config
> ### Use it and exit with an error if:
> #### File doesn't exist
> #### Node in config doesn't exist (default being default node or the one
> specified via --node)
> ## default config file (~/.rabbitmqadmin.conf)
> ### If file doesn't exist, just ignore it.
> ### If file exists and node in file doesn't exist
> #### exit showing that error message
Does this mean rabbitmqadmin will fail if the default file exists, and
the user does not specify a node, and the file does not contain a
default node? That seems wrong.
Other than that this sounds reasonable.
> # Options on the command line
>
> This would also overwrite any options (last parsed "wins").
Yes.
Cheers, Simon
--
Simon MacMullen
RabbitMQ, VMware
More information about the rabbitmq-discuss
mailing list