From 4115c6ac2ff15f9eaa0fa3247a12963b9a9547c3 Mon Sep 17 00:00:00 2001 From: Dmitriy Rabotyagov Date: Fri, 18 Oct 2024 16:19:18 +0200 Subject: [PATCH] [reno] Add a release note for haproxy_limit_hosts key implementation Depends-On: https://review.opendev.org/c/openstack/openstack-ansible-plugins/+/931772 Change-Id: Ic7ef741888dccd1a233e1e11fca1889d8781e600 --- .../haproxy_limit_hosts-0f529297c9748eb7.yaml | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 releasenotes/notes/haproxy_limit_hosts-0f529297c9748eb7.yaml diff --git a/releasenotes/notes/haproxy_limit_hosts-0f529297c9748eb7.yaml b/releasenotes/notes/haproxy_limit_hosts-0f529297c9748eb7.yaml new file mode 100644 index 0000000000..fb9bac8d08 --- /dev/null +++ b/releasenotes/notes/haproxy_limit_hosts-0f529297c9748eb7.yaml @@ -0,0 +1,20 @@ +--- +features: + - | + A mapping ``_haproxy_services`` now can contain a key + ``haproxy_limit_hosts``, which can be used to filter out haproxy + nodes to which this config should be applied. + This behaviour might be useful in case you want to apply a different + service configuration to haproxy hosts. +fixes: + - | + Functionality of providing different haproxy service settings per haproxy + host has been restored through ``haproxy_limit_hosts`` key which provides + filtering of target HAProxy hosts, to which this configuration should be + applied. + Before moving ``_haproxy_services`` from `haproxy_all` group_vars + it was possible to supply a completely independent set of backends + that will be configured on the HAProxy server. + With moving backend defenition to specific service group_vars, this ability + was lost, as there was no way to tell what config to apply to which HAProxy + server.