relation config values set to the empty string are lost
Bug #1379930 reported by
Aaron Bentley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Expired
|
Medium
|
Unassigned | ||
Bug Description
When relation set is called to set a value to "", it instead ignores the value entirely. This is a discontinuity-- it makes the behaviour of the empty string is different from the behaviour of all other strings. It means that special handling is required where it otherwise might not be.
It also makes code fail in surprising ways-- when charm A gets a value from an external source and then transmits it to charm B, charm B will suddenly start failing if the external source provides the empty string and so the value is not present.
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju-core: | |
| milestone: | none → 1.21-alpha2 |
| tags: | added: charm relations |
| Changed in juju-core: | |
| milestone: | 1.21-alpha2 → 1.21-alpha3 |
| Changed in juju-core: | |
| importance: | High → Medium |
| milestone: | 1.21-alpha3 → none |
Revision history for this message
| Curtis Hovey (sinzui) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju-core: | |
| status: | Incomplete → Expired |
To post a comment you must log in.
This bug might be fixed in master. a recent change revealed that Juju was sending config keys with empty values when relations changed.