meaning of default in 'juju config' output is ambiguous
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia |
Bug Description
'juju config' uses 'default' to apparently mean "the value of this
config option is the same as the default", but it could very easily be
read as "the default value of this config option is 'true'". e.g.:
| osd-encrypt:
| default: true
| description: |
| By default, the charm will not encrypt Ceph OSD devices; however, by
| setting osd-encrypt to True, Ceph's dmcrypt support will be used to
| encrypt OSD devices.
| .
| Specifying this option on a running Ceph OSD node will have no effect
| until new disks are added, at which point new disks will be encrypted.
| type: boolean
| value: false
If the name was 'is_default' (for example), this would remove the
ambiguity.
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Would is_default or default_value be more useful in this case?