Pass SSL options down to AMQP.Connection.open/2

[jeffhsta]

As of now I have an Elixir service running on Elixir 1.14 OTP 25 and when I bump it to Elixir 1.15 OTP 26 I start getting an RabbitMQ connection error. After some investigation I see that is caused by an OTP change where the default SSL parameter were changed.

I am using AWS managed RibbitMQ that forces me to open a connection over SSL using ampqs protocol and I was able to make it work by calling AMQP.Connection.open("my-rabbitmq-url", ssl_options: [verify: :verify_none, fail_if_no_peer_cert: false]).

But I released that using BroadwayRabbitMQ I get the same issue I was getting before when doing AMQP.Connection.open("my-rabbitmq-url"), since now I need to pass the SSL options.

According to this line of code, it seems like there is no options being passed down to AMQP connection.

I am wondering what would be the best way to solve this issue.

I see two easy ways:

• Allow the ssl_options to be passed down
• Allow BroadwayRabbitMQ.Producer to receive on connection param not only a URL or a Keyword, but also an RabbitMQ Connection that was previously openned.

Thoughts?

[josevalim]

A PR that explores passing all options forward to AMQP would be welcome!