[rabbitmq-discuss] rabbitmqadmin and default node behaviour

[Simon Lundström]

On Tue, 2012-10-30 at 10:53:35 +0000, Simon MacMullen wrote:
> 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?

Exactly.

This is a small price to pay, IMO, compared to always having to specify
either the node or a config file.

> That seems wrong.

How would you propose it should work? The only solutions I can come up
with is the one that currently exists and the one that I propose.

Thanks,
- Simon