The Juju GUI doesn't use juju unset for config updates
Bug #1279414 reported by
Jeff Pihach
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-gui |
Triaged
|
Low
|
Unassigned | ||
Bug Description
At the moment input fields in config options are converted to `null` if their value is "" before being sent to Juju (see views/utils.
Still unanswered: Can boolean values be unset? Can a config option be configured as a boolean but without a default?
| description: | updated |
| description: | updated |
| Changed in juju-gui: | |
| importance: | Undecided → Low |
| Changed in juju-gui: | |
| status: | New → Triaged |
To post a comment you must log in.
