[05:31] <blr> wgrant: are you aware of an alternative to setting juju config via juju deployer (i.e. the 'deploy' yaml in mojo) in a spec?
[05:32] <blr> a manual juju set in postdeploy?
[05:33] <wgrant> blr: I've just had sysadmins run juju set manually in the past.
[05:33] <wgrant> What're you trying to do?
[05:34] <blr> wgrant: updating rutabaga's mojo spec to reflect the changes we made to auth_params in the charm a while back, and I think there is possibly a bug in juju in that it appears to strip quotes when passing the list of dicts to juju deployer, which blows up
[05:34] <blr> Invalid config charm squid-forwardproxy auth_params=[{'scheme': 'basic', 'program': '/srv/rutabaga/code/rutabaga/scripts/rutabaga_auth_helper.py'}]
[05:35] <blr> juju set squid-forwardproxy auth_params="[{'scheme': 'basic', 'program': '/srv/rutabaga/code/rutabaga/scripts/rutabaga_auth_helper.py'}]" is fine however
[05:37] <blr> escaping quotes results in yaml errors
[05:49] <blr> hmm double quoting the string passes the correct string, yet juju deployer still complains. Invalid config charm squid-forwardproxy auth_params='[{'scheme': 'basic', 'program': '/srv/rutabaga/code/rutabaga/scripts/rutabaga_auth_helper.py'}]'
[05:56] <wgrant> blr: Are you sure your version of the charm has that parameter?
[05:59] <blr> wgrant: it does, the correct rev of the charm is in the build directory
[05:59] <wgrant> blr: What's your syntax in the YAML?
[06:01] <blr> http://paste.ubuntu.com/12203792/
[06:02] <wgrant> blr: I used syntax like this to avoid escaping issues:
[06:02] <wgrant>   auth_params: |
[06:02] <wgrant>     [some, literal, yaml]