Activity log for bug #1279414
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2014-02-12 16:38:16 | Jeff Pihach | bug | added bug | ||
| 2014-02-12 16:38:29 | Jeff Pihach | description | At the moment input fields in config options are convered to `null` if their value is "" before being sent to Juju (see views/utils.js:_getElementsValuesMapping()). We may be able to simply check for these null values and use the `juju unset` api call to unset them. Still unanswered: Can boolean values be unset? Can a config option be configured as a boolean but without a default? | At the moment input fields in config options are converted to `null` if their value is "" before being sent to Juju (see views/utils.js:_getElementsValuesMapping()). We may be able to simply check for these null values and use the `juju unset` api call to unset them. Still unanswered: Can boolean values be unset? Can a config option be configured as a boolean but without a default? | |
| 2014-02-12 16:58:42 | Jeff Pihach | 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.js:_getElementsValuesMapping()). We may be able to simply check for these null values and use the `juju unset` api call to unset them. Still unanswered: Can boolean values be unset? Can a config option be configured as a boolean but without a default? | At the moment input fields in config options are converted to `null` if their value is "" before being sent to Juju (see views/utils.js:_getElementsValuesMapping() and then views/utils.js:getChangedConfigOptions()). We may be able to simply check for these null values and use the `juju unset` api call to unset them. Still unanswered: Can boolean values be unset? Can a config option be configured as a boolean but without a default? | |
| 2014-02-24 14:53:47 | Richard Harding | juju-gui: importance | Undecided | Low | |
| 2014-07-14 19:46:19 | Curtis Hovey | juju-gui: status | New | Triaged |
