LWRP for managing exchanges using rabbitmq api client

[cmluciano]

Refactor #118 using https://github.com/ruby-amqp/rabbitmq_http_api_client

[josacar]

@cmluciano I wonder why these new providers use a Gem and others use plain CLI. I consider HTTP APIs more stable than CLIs, but I wonder how we can contribute to add queues, exchanges and bindings support in this cookbook.

[jsirex]

:+1:

[nickkeyzer]

:+1:

[michaelklishin]

I don't think there's much opposition to doing this. rabbitmqctl does not manage topology items (e.g. queues), however, only rabbitmadmin does (which comes with the management plugin and relies on its API).

Key issue here is that this cookbook needs to

• Have a node with the plugin enabled booted
• Have the permissions to connect to it on the correct port

The latter will vary from system to system and this cookbook cannot make too many assumptions about that.

Please refrain from making bold claims that "HTTP APIs are more stable than CLIs" unless you can provide evidence backed by data.

[michaelklishin]

Also, definitions import may be a worthwhile alternative to use here. It's still an HTTP API call, however.

"Automatic" (on boot) definitions import from a static JSON file is also supported by RabbitMQ but since it happens on boot, things can get quite tricky for plugins, e.g. Shovel definitions, because there's a chichen-and-egg problem between definitions import and plugin activation. There's no obvious solution to this at the moment.

[michaelklishin]

Definitions import are now supported and are a much better way if you ask me.