Add rabbitmq_ssl parameter to enable SSL transport to RabbitMQ #249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This new parameter enables SSL transport when connecting to RabbitMQ. This way
you can use SSL to connect to RabbitMQ without configuring it for certificate
authentication (rabbitmq_ssl_private_key and rabbitmq_ssl_cert_chain parameters.)
If you have rabbitmq_ssl => true with no other rabbitmq_ssl parameters, the
rabbitmq.json config file will have an empty ssl { } stanza in it. This makes
Sensu use SSL transport when connecting to RabbitMQ, but it will not attempt
certification authentication.