Upgrade to 2.6

[tswicegood]

RabbitMQ decided that a minor version bump was time to break rabbitmqctl. :-( I've tested this against RabbitMQ 2.6. It obviously doesn't work against < 2.6.

Edit: The break was in RabbitMQ 2.6.

[tswicegood]

I've thought about abstracting out the rabbitmqctl code as well so you can specify a version if you want to run the old version for some specific reason. Thoughts?

[rajesh-kumar]

How about, adding the support for work queues configuration on RabbitMq in coming versions?

[tswicegood]

I'm not opposed, but I think that's probably worth a separate PR since this currently is a fix instead of a feature.

[rajesh-kumar]

I Agree!!

[dcarley]

Is there any interest in keeping backwards compatibility with previous versions?

[bodepd]

what version are you looking for support for?

I was going to create branches with version names so that multiple versions can be maintained in multiple branches.

[dcarley]

I have some installs on 2.2 because that is what's in EPEL.

Would it be better to just switch behaviour/features based on a version Fact?

[nikdoof]

Slight issue with this pull, its possible for other values to appear in the list_users (on RabbitMQ 2.6.1) output than just administrator or none:

amqp:~# rabbitmqctl  list_users
Listing users ...
dreddit [management]
processadmin [administrator]
intelapi        [management]
...done.

Fixing the match line in the admin check to the following resolves the issue but i'm not sure if its the best method to be using here

line.match(/^#{resource[:name]}\s+\[(administrator|.*)?\]/)