File given to deploy --config is incompatible with pyjuju

[William Reade]

The yaml file given to deploy --config <file.yaml> that pyjuju expects needs to have a key with the service name, while the one given to juju-core must not have such a key. For example, the landscape-client charm config:

pyjuju:
"""
landscape-client:
    url: https://landscape.canonical.com/message-system
"""

gojuju:
"""
url: https://landscape.canonical.com/message-system
"""

[Andreas Hasenack (ahasenack)]

The --config parameter is in the deploy documentation (juju deploy -h), but doesn't work.

[Sidnei da Silva (sidnei)]

Best I can tell, the problem is that the expected contents for the --config file are different between pyjuju and gojuju.

pyjuju expects (supports?) a top-level key that matches the service name such that you can have the config for all services into a single file, as in:

u1-3rdparty-fe:
    enable_modules: proxy rewrite proxy_http proxy_balancer ssl headers
    servername: 3rdpartymedia.ubuntuone.com
u1-public-fe:
    enable_modules: proxy rewrite proxy_http proxy_balancer ssl headers
    servername: ubuntuone.com

gojuju does not look for that top-level key, and instead expects the config settings to be at the top-level. as a result, if you have the service name at top-level, the config settings are ignored and no error is logged/printed. eg:

enable_modules: proxy rewrite proxy_http proxy_balancer ssl headers
servername: 3rdpartymedia.ubuntuone.com