I experienced some issues when trying to have two Bunny instances at the same time, where one would be instantiated using Bunny.new (with a connection string set in the RABBITMQ_URL environment variable) and the other would be instantiated using Bunny.new(some_connection_string). Apparently both instances would then use the connection string from the RABBITMQ_URL environment variable.
This PR is a fix to that issue, so when a Bunny is instantiated given a specific connection string (or hash), it will disregard the RABBITMQ_URL environment variable and when Bunny is instantiated without a connection argument, it will default to use value of a look-up of the RABBITMQ_URL environment variable.
Default to ENV['RABBITMQ_URL'] when no connection argument is given
- Bunny.new and Bunny.run now defaults to ENV['RABBITMQ_URL'] for connection
- Session.new now only uses ENV['RABBITMQ_URL'] for connection argument
when no other argument is given.
Highlight #403 in release notes, references #435