373b9bb0f2
We do allow to supply haproxy_backend_nodes as list of mappings rather the regular list, which supports `ip_addr`, `name` and `backend_port` keys. However, we do verify hostvars[host_name] and try to set ip_addr regardless if this needed or not. During hostvars[host_name] request Ansible tries to fetch all host variables and resolve some of them, which not always can be possible or preffered in some scenarios. Good example of that would be Mozilla SOPS [1] encrypted variables for specific host or group, which can not be decrypted by some operators. In the meanwhile they can be eligible to configure haproxy frontend/backend for this service. So we should have a way to avoid asking for specific hostvars when it's not needed, and backend_nodes are already contain all required information. [1] https://docs.ansible.com/ansible/latest/collections/community/sops/docsite/guide.html Change-Id: I17a7f2421cd31b37bbda4f9c85971b1825e54891
Team and repository tags
OpenStack-Ansible HAProxy server
- Documentation for the project can be found at:
-
https://docs.openstack.org/openstack-ansible-haproxy_server/latest
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-haproxy_server/
- The project source code repository is located at:
-
https://opendev.org/openstack/openstack-ansible-haproxy_server/
- The project home is at:
- The project bug tracker is located at: