From 66b3736654a459e4426a82a0200cbb20e39c8e2b Mon Sep 17 00:00:00 2001 From: Dmitriy Rabotyagov Date: Thu, 26 Oct 2023 18:28:25 +0200 Subject: [PATCH] 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 --- inventory/group_vars/all/all.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/inventory/group_vars/all/all.yml b/inventory/group_vars/all/all.yml index 04647df40b..cc916f9de0 100644 --- a/inventory/group_vars/all/all.yml +++ b/inventory/group_vars/all/all.yml @@ -146,4 +146,4 @@ venv_build_host_user_name: "{{ repo_service_user_name }}" venv_build_host_group_name: "{{ repo_service_group_name }}" # Set RabbitMQ management UI to use TLS -rabbitmq_management_ssl: true +rabbitmq_management_ssl: "{{ haproxy_ssl }}"