Code review comment for lp://qastaging/~simpoir/landscape-charm/bionic-source-build

Deployment of charm went smoothly, as did deployment and relation of postgresql and rabbitmq-server. Hit a snag with haproxy though: deployed fine but fails to relate complaining it can't find an SSL cert:

unit-haproxy-1: 21:46:09 DEBUG unit.haproxy/1.reverseproxy-relation-changed [ALERT] 207/204609 (6354) : parsing [/etc/
haproxy/haproxy.cfg:59] : 'bind 0.0.0.0:443' : unable to load SSL certificate file '/var/lib/haproxy/default.pem' file
 does not exist.
unit-haproxy-1: 21:46:09 DEBUG unit.haproxy/1.reverseproxy-relation-changed [ALERT] 207/204609 (6354) : Parsing [/etc/
haproxy/haproxy.cfg:129]: frontend 'haproxy-1-80' has the same name as frontend 'haproxy-1-80' declared at /etc/haprox
y/haproxy.cfg:22.
unit-haproxy-1: 21:46:09 DEBUG unit.haproxy/1.reverseproxy-relation-changed [ALERT] 207/204609 (6354) : Error(s) found
 in configuration file : /etc/haproxy/haproxy.cfg
unit-haproxy-1: 21:46:09 DEBUG unit.haproxy/1.reverseproxy-relation-changed [ALERT] 207/204609 (6354) : Fatal errors f
ound in configuration.
unit-haproxy-1: 21:46:09 INFO unit.haproxy/1.juju-log reverseproxy:7: HAProxy configuration check failed, exiting.
unit-haproxy-1: 21:46:09 ERROR juju.worker.uniter.operation hook "reverseproxy-relation-changed" failed: exit status 1

I wonder if that's expected though; something the deployer is meant to provide?