meaning of default in 'juju config' output is ambiguous

[James Troup]

'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.

[Witold Krecicki (wpk)]

Would is_default or default_value be more useful in this case?

[James Troup (elmo)]

Witold Krecicki <email address hidden> writes:

> Would is_default or default_value be more useful in this case?

Either would be more useful than the current situation, yes.

--
James

[Anastasia (anastasia-macmood)]

There is more discussion around this topic on bug # 1697837.

However, I'll keep this bug dedicated to just how/if to display that the value is the same as defined on charm, i.e. currently known as "default".

[Paul Gear (paulgear)]

Possibly a dup of https://bugs.launchpad.net/juju-core/+bug/1496639 ?

[Anastasia (anastasia-macmood)]

@Paul Gear (paulgear),

This is not a dupe of bug # 1496639. That report was about regression and was a functional failure. This report is just about fixing how we display, specifically labeling, of values in the output.

I agree - "is_default" is a lot clearer \o/

[Anastasia (anastasia-macmood)]

PR against develop: https://github.com/juju/juju/pull/7723

[Anastasia (anastasia-macmood)]

Doc issue created - https://github.com/juju/docs/issues/2023