Merge lp:~jimbaker/pyjuju/juju-get-cli-use-yaml-null into lp:pyjuju
Proposed by
Jim Baker
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Jim Baker | ||||
Approved revision: | 577 | ||||
Merged at revision: | 577 | ||||
Proposed branch: | lp:~jimbaker/pyjuju/juju-get-cli-use-yaml-null | ||||
Merge into: | lp:pyjuju | ||||
Diff against target: |
25 lines (+2/-2) 2 files modified
juju/control/config_get.py (+1/-1) juju/control/tests/test_config_get.py (+1/-1) |
||||
To merge this branch: | bzr merge lp:~jimbaker/pyjuju/juju-get-cli-use-yaml-null | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Clint Byrum (community) | Approve | ||
Review via email: mp+124281@code.launchpad.net |
Description of the change
juju get should use standard YAML for null value
The juju get command for retrieving config settings currently uses a custom value of -Not set- to imply None (Python)/nil (golang), instead of just using YAML's support for a null value. This bug means that it's not possible to distinguish a user setting of this string of -Not set-, which prevents roundtripping on that specific value.
To post a comment you must log in.
Please take a look.