9451ac61a0
This allows for more config flexibility - e.g. running multiple backends with a common frontend. It is not possible with the 'listen' approach (which enforces frontend). Additionally, it does not really make sense to support two ways to do the exact same thing as the process is automated and 'listen' is really meant for humans not willing to write separate sections. Hence this deprecates 'listen' variant. At the moment both templates work exactly the same. The real flexibility comes in following patches. Note this is a building block for future work on letsencrypt validator (which should offer backend and share frontend with any service running off 80/443 - which would be only horizon in the current default config), as well as any work towards single port (that is single frontend) and multiple services anchored at paths of it (which is the new recommended default). Change-Id: I2362aaa3e8069fe146d42947b8dddf49376174b5 Partially-Implements: blueprint letsencrypt-https
18 lines
572 B
YAML
18 lines
572 B
YAML
---
|
|
project_name: "haproxy-config"
|
|
|
|
# DEPRECATED(yoctozepto): using "haproxy_single_service_listen.cfg.j2" here is deprecated
|
|
haproxy_service_template: "haproxy_single_service_split.cfg.j2"
|
|
|
|
# Extra frontend/backend options (additive with locally defined options)
|
|
haproxy_frontend_http_extra:
|
|
- "option httplog"
|
|
- "option forwardfor"
|
|
haproxy_frontend_tcp_extra:
|
|
- "option tcplog"
|
|
haproxy_backend_http_extra: []
|
|
haproxy_backend_tcp_extra: []
|
|
|
|
haproxy_health_check: "check inter 2000 rise 2 fall 5"
|
|
haproxy_health_check_ssl: "check check-ssl inter 2000 rise 2 fall 5"
|