I was able to deploy the vanilla haproxy charm with the following yaml file:
melmoth@x220:~/dev/spip-juju$ cat spip.yaml haproxy: default_timeouts: "queue 7000, connect 7000, client 7000, server 7000" services: | - service_name: haproxy_service service_host: "0.0.0.0" service_port: 80 service_options: [balance leastconn , appsession spip_session len 34 timeout 3h request-learn] server_options: maxconn 100 spip: spip-origin: 3.0.5
The haproxy.cfg configuration file ends up with the same content as what it would have been using the merge proposal and setting listen_appsession to 'spip_session len 34 timeout 3h request-learn'
Looks to me the merge request is not needed.
« Back to merge proposal
I was able to deploy the vanilla haproxy charm with the following yaml file:
melmoth@ x220:~/ dev/spip- juju$ cat spip.yaml timeouts: "queue 7000, connect 7000, client 7000, server 7000"
service_ host: "0.0.0.0"
service_ port: 80
service_ options: [balance leastconn , appsession spip_session len 34 timeout 3h request-learn]
server_ options: maxconn 100
haproxy:
default_
services: |
- service_name: haproxy_service
spip:
spip-origin: 3.0.5
The haproxy.cfg configuration file ends up with the same content as what it would have been using the merge proposal and setting listen_appsession to 'spip_session len 34 timeout 3h request-learn'
Looks to me the merge request is not needed.