juju get should use standard YAML for null value
Bug #1050555 reported by
Jim Baker
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Fix Released
|
Medium
|
Jim Baker | ||
Bug Description
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.
Related branches
lp:~jimbaker/pyjuju/juju-get-cli-use-yaml-null
- Clint Byrum (community): Approve
-
Diff: 25 lines (+2/-2)2 files modifiedjuju/control/config_get.py (+1/-1)
juju/control/tests/test_config_get.py (+1/-1)
| Changed in juju: | |
| assignee: | nobody → Jim Baker (jimbaker) |
| milestone: | none → 0.7 |
| status: | New → In Progress |
| Changed in juju: | |
| importance: | Undecided → Medium |
| milestone: | 0.7 → 0.6 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
