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
(cherry picked from commit afa12fbc97
)
This commit is contained in:
parent
3a0d672751
commit
7aef92403c
|
@ -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``.
|
|
@ -82,7 +82,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 %}
|
||||
|
|
Loading…
Reference in New Issue