While it is possible to configure client TLS options via the ssl app, it is very obscure to non-Erlang users.
A standard set of TLS options should be exposed via a common set of Cuttlefish options, ideally in a way that doesn't interfere with other plugins, libraries or tools (in Cuttlefish only one key is allowed for one target key).
While it is possible to configure client TLS options via the
ssl
app, it is very obscure to non-Erlang users.A standard set of TLS options should be exposed via a common set of Cuttlefish options, ideally in a way that doesn't interfere with other plugins, libraries or tools (in Cuttlefish only one key is allowed for one target key).
See https://github.com/rabbitmq/rabbitmq-peer-discovery-consul/issues/14 for background.