42d80464af
Currently default_backend for a service is always set to the haproxy_service_name for a service, but this might not be what is required for some configurations. This patch allows haproxy_default_backend to be configured for a service to customise the default_backend setting. Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-rabbitmq_server/+/876436 Change-Id: I9e2be37cb27a33350577a93f23b69e560493b320
11 lines
501 B
YAML
11 lines
501 B
YAML
---
|
|
features:
|
|
- |
|
|
A new key ``haproxy_default_backend`` can be defined for each service
|
|
configured in the haproxy loadbalancer. Configuring this variable writes
|
|
a value for the ``default_backend`` directive into the config for the
|
|
service frontend. It can be useful to provide a specific default backend
|
|
as a fall-through option when other backends are selected using ACLs,
|
|
and to also allow the name of the default backend to be different from
|
|
``haproxy_service_name``.
|