juju config hides value if the value is null/empty
Bug #1709695 reported by
James Troup
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
Bug Description
juju config doesn't display 'value' at all in the output for a config option if it's set to null/empty. This is confusing if you don't know it does that.
| Changed in juju: | |
| milestone: | none → 2.3-alpha1 |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.3-beta1 → 2.3-beta2 |
| Changed in juju: | |
| assignee: | nobody → Eric Claude Jones (ecjones) |
| Changed in juju: | |
| assignee: | Eric Claude Jones (ecjones) → nobody |
Revision history for this message
| Tim Penhey (thumper) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Incomplete |
| Changed in juju: | |
| milestone: | 2.3-beta2 → none |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju: | |
| status: | Incomplete → Expired |
| Changed in juju: | |
| status: | Expired → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
In the 2.3 branch now, when asking for config, there is now a source key. This source will say "unset", "default", or "user".
If the charm config has a default value, this value is also returned with the key "default".
If the value is null, it is not returned, and the source says "unset".
If the value of the option hasn't been set, but there is a default value, the source will be "default", and the value will match the default value.
If the value of the option has been set, the source will say "user", even if the value matches the current charm default.
Is this sufficiently clear to close this bug now?