differing behavior with pyjuju: config-get all json

[David Britton]

PY JUJU:

config-get all: {"log-level": "DEBUG"}

JUJU-CORE:

config-get all: {"account-name":null,"autodiscover-a-query-string":null,"autodiscover-srv-query-string":null,"data-path":null,"exchange-interval":null,"http-proxy":null,"https-proxy":null,"include-manager-plugins":null,"log-dir":null,"log-level":"DEBUG","origin":null,"ping-interval":null,"ping-url":null,"registration-key":null,"script-users":null,"server-autodiscover":null,"ssl-public-key":null,"tags":null,"urgent-exchange-interval":null,"url":null}

juju-core returns all items even if not set. I'm not sure if this change was intended. I can't really see much value for it, and it does require at least us to change our charm to account for this modification (maybe other teams and individuals would need to do the same). If this is easily fixable in core, it might make sense to do it.

Querying individual values through config-get behaves the same in both juju core and pyjuju. I'll attach a full log showing both outputs.

[David Britton (dpb)]

Full output if interested on what happens when you query unset configs in different ways.

PY JUJU:

2013-06-19 21:56:35,411: hook.output@INFO: all: {"log-level": "DEBUG"}
data-path:
data-path(json): null

JUJU-CORE:

2013-06-19 22:08:57 INFO juju context.go:221 worker/uniter: HOOK all: {"account-name":null,"autodiscover-a-query-string":null,"autodiscover-srv-query-string":null,"data-path":null,"exchange-interval":null,"http-proxy":null,"https-proxy":null,"include-manager-plugins":null,"log-dir":null,"log-level":"DEBUG","origin":null,"ping-interval":null,"ping-url":null,"registration-key":null,"script-users":null,"server-autodiscover":null,"ssl-public-key":null,"tags":null,"urgent-exchange-interval":null,"url":null}
2013-06-19 22:08:57 INFO juju context.go:221 worker/uniter: HOOK data-path:
2013-06-19 22:08:57 INFO juju context.go:221 worker/uniter: HOOK data-path(json): null