Map default value of rabbitmq_management_ssl to haproxy_ssl

At the moment all haproxy backends are defined if TLS should be used by
using `haproxy_ssl` variable. If deployer don't want to have SSL, they
are supposed to use the variable for that. However, the only service that
is not respecting that is RabbitMQ management interface.

As a result haproxy fails with the invalid configuration, since
certificates are not provisioned when `haproxy_ssl` is False.
So configuration at the end is invalid as reffer to the certificate
that does not exist on the host and was not even issued.

Change-Id: Idc924d4ee485c8e6efc15b90df90ba5021a106e4
This commit is contained in:
Dmitriy Rabotyagov 2023-10-26 18:28:25 +02:00
parent 512c445073
commit 66b3736654

View File

@ -146,4 +146,4 @@ venv_build_host_user_name: "{{ repo_service_user_name }}"
venv_build_host_group_name: "{{ repo_service_group_name }}" venv_build_host_group_name: "{{ repo_service_group_name }}"
# Set RabbitMQ management UI to use TLS # Set RabbitMQ management UI to use TLS
rabbitmq_management_ssl: true rabbitmq_management_ssl: "{{ haproxy_ssl }}"