[rabbitmq-discuss] rabbitmqadmin and default node behaviour

Tim Watson tim at rabbitmq.com
Thu May 30 13:18:45 BST 2013


Hi Simon!

I'm going to QA your changes this week, but I won't be able to send you the agreement (and then merge them) until I get hold of the latest copy. Bear with me - I'll try and make sure this happens before the next release! :D

Cheers,
Tim 

On 29 May 2013, at 12:41, Simon Lundström wrote:

> Hi Tim!
> 
> No, I haven't signed any contributor agreement, please advice.
> 
> (As per GitHub pull request)
> 
> Br,
> - Simon
> 
> On Fri, 2013-05-24 at 16:43:09 +0200, Simon Lundström wrote:
>> On Mon, 2012-11-05 at 14:10:23 +0000, Simon MacMullen wrote:
>>> On 30/10/12 12:12, Simon Lundström wrote:
>>>> So basically:
>>>> 
>>>> Parse the config/defaults in this order:
>>>> # defaults from default_options hash^Wdictionary
>>>> # config file
>>>> ## Find out which config file to use, one of:
>>>> ### specified via --config
>>>> #### Use it and exit with an error if it doesn't exist
>>>> ### default config file (~/.rabbitmqadmin.conf)
>>>> #### If file doesn't exist, just ignore it.
>>>> ## If node doesn't exist in config and is:
>>>> ### specified via commandline
>>>> #### Display error and exit
>>>> ### using the default node
>>>> #### ignore the config file entirely
>>>> # Options on the command line
>>> 
>>> Yes, I think that makes sense.
>> 
>> Sorry for taking so long, been busy on other things = )
>> 
>> I've patched this and created a PR on Github (see
>> <https://github.com/rabbitmq/rabbitmq-management/pull/6>)
>> 
>> Please tell me if you prefer patches some other way.
>> 
>> Have a great weekend!



More information about the rabbitmq-discuss mailing list