Comment 2 for bug 1892423

We seem to have hit this bug today while deploying a mojo manifest containing:

haproxy:
  options:
    services: include-file://{{spec_dir}}/{{stage}}/../configs/haproxy.cfg

"haproxy.cfg" being a file containing valid yaml data.

Instead of the expected result (haproxy.cfg being parsed and the values correctly propagating `juju config haproxy services`), what we saw was the entire contents of that file being wrapped as a binary string, e.g.:

$ juju config haproxy services
b'- service_name: service\n service_host: "0.0.0.0"\n service_port: 443\n service_options:\n - mode http\n - balance leastconn\n - cookie SRVNAME insert\n'

This bug does not appear to occur for another spec that includes haproxy configuration in the same manner, but does it in a bundle phase instead of a deploy phase.