Different behavior on ServiceDeploy with Config/ConfigYAML
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Juju behaves differently when a config option with an empty string as value is passed to the "ServiceDeploy" API call whether the configuration is passed via "Config" or "ConfigYAML" parameters.
With a charm with the following config:
options:
some-option:
type: string
default: some value
When deploying the charm, I want to set some-option to empty string. If I do this setting the value in the "Config" parameter of the deploy call, juju interprets this as unsetting the key, and the charm gets the default value instead.
Passing the empty string value in "ConfigYAML" actually passes an empty string to the charm.
This can be tested with jujuclient for instance, which uses the Config parameter.
tags: | added: kanban-cross-team |
tags: | removed: kanban-cross-team |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: landscape |
tags: | added: 2.0-count |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
This issue may relate to bug 1379930