Fix inconsistency in haproxy_frontend_raw naming
We have announced and documented haproxy_frontend_raw variable while in fact introduced haproxy_raw. Since announced variable name better reflects its purpose and it was announced, we rename it to haproxy_frontend_raw in template generation. Change-Id: I7ba9588b599f42dddad395df1a2e18ccfe6b3fe3
This commit is contained in:
2 changed files with 7 additions and 1 deletions
@@ -0,0 +1,6 @@
---
fixes:
- |
Fixed inconsistency in ``haproxy_frontend_raw`` key naming between
documentation and service template. Previously, template generation
was expecting ``haproxy_raw`` instead of the ``haproxy_frontend_raw``.
@@ -71,7 +71,7 @@ frontend {{ item.service.haproxy_service_name }}-front-{{ loop.index }}
{% if not item.service.haproxy_frontend_only | default(false) %}
default_backend {{ item.service.haproxy_service_name }}-back
{% endif %}
{% for entry in item.service.haproxy_raw|default([]) %}
{% for entry in item.service.haproxy_frontend_raw|default([]) %}
{{ entry }}
{% endfor %}
{% endfor %}
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.