Do not restart RabbitMQ for Policy Change

[bdwyertech]

Addresses #441

We don't have to restart RabbitMQ to apply policies.

The changes in #425 will cause these notifications to fire on every Chef run.

Straight from https://www.rabbitmq.com/parameters.html

Policies can change at any time. 
When a policy definition is updated, its effect on matching exchanges and queues will be reapplied.
Usually it happens instantaneously but for very busy queues can take a bit of time (say, a few seconds).

[michaelklishin]

@jjasghar LGTM. Should I merge?

[jjasghar]

I'll release a new version soon. I'm going to revisit the PRs and ideally get a new release cut on the 18th.

[bdwyertech]

Stop working on holidays :-)

…

On Sun, May 14, 2017, 19:44 JJ Asghar ***@***.***> wrote: I'll release a new version soon. I'm going to revisit the PRs and ideally get a new release cut on the 18th. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#445 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC1eWUmYRvyKA3_bzsZy33Vjn9o-vsv9ks5r55HPgaJpZM4NaQkd> .