I think it would be nice if juju status
could provide the charm configuration. Maybe a new command option --show-config
can be created. As far as I know, right now the only way to get the charm configuration is through juju export-bundle
.
You can also juju config <application name>
to show the configuration names, their values, and descriptions.
Example:
$ juju config slurmd
application: slurmd
application-config:
trust:
default: false
description: Does this application have access to trusted credentials
source: default
type: bool
value: false
charm: slurmd
settings:
custom-slurm-repo:
default: ""
description: |
Use a custom repository for Slurm installation.
This can be set to the Organization's local mirror/cache of packages and supersedes the Omnivector repositories. Alternatively, it can be used to track a `testing` Slurm version, e.g. by setting to `ppa:omnivector/osd-testing` (on Ubuntu), or `https://omnivector-solutions.github.io/repo/centos7/stable/$basearch` (on CentOS).
Note: The configuration `custom-slurm-repo` must be set *before* deploying the units. Changing this value after deploying the units will not reinstall Slurm.
source: default
type: string
value: ""
nhc-conf:
default: ""
description: |
Custom extra configuration to use for Node Health Check.
These lines are appended to a basic `nhc.conf` provided by the charm.
source: default
type: string
value: ""
partition-config:
default: ""
description: |
Extra partition configuration, specified as a space separated `key=value` in a single line.
Example usage: $ juju config slurmd partition-config="DefaultTime=45:00 MaxTime=1:00:00"
source: user
type: string
value: OverSubscribe=YES
partition-name:
description: |
Name by which the partition may be referenced (e.g. `Interactive`).
Note: The partition name should only contain letters, numbers, and hyphens. Spaces are not allowed.
source: unset
type: string
partition-state:
default: UP
description: |
State of partition or availability for use. Possible values are `UP`, `DOWN`, `DRAIN` and `INACTIVE`. The default value is `UP`. See also the related `Alternate` keyword.
source: default
type: string
value: UP
Thanks Heitor. I forgot to mention this way of getting the config from a charm, but in the project that I’m working (juju-lint) I need the information from the whole model that will be the input to the CLI. E.g:
juju status --format yaml > status.yaml
juju-lint status.yaml
Actually the juju-lint charm takes the output from export bundle and juju status, so everything is covered, but I still think it would be nice to have a way of showing the configuration of all charms in juju status