Juju command to display non-default config values

Bug #1975748 reported by Connor Chamberlain
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Opinion
Wishlist
Unassigned

Bug Description

There are times when it would be convenient to quickly see which configs for a given application have a non-default value. Currently, we can achieve this effect by performing an export-bundle, but it is slow and wasteful for this purpose, as it generates far more data than is required.

I would like to be able to run something like `juju config $app --non-default` or `juju non-default-configs $app` and see all configs for $app which have been modified.

Changed in juju:
importance: Undecided → Wishlist
status: New → Opinion
Revision history for this message
Nobuto Murata (nobuto) wrote :

Fwiw, Juju keeps "source: user" for those values modified by an user so you can query it like:

$ juju config keystone --format json \
    | jq -c '.settings | to_entries[] | select(.value.source=="user").key'

"openstack-origin"
"os-admin-hostname"
"os-internal-hostname"
"os-public-hostname"
"region"
"vip"

$ juju config keystone --format json \
    | jq -c '.settings | to_entries[] | select(.value.source=="user") | [.key, .value.value]'

["openstack-origin","cloud:focal-yoga"]
["os-admin-hostname","admin.my.example.com"]
["os-internal-hostname","internal.my.example.com"]
["os-public-hostname","public.my.example.com"]
["region","myRegion"]
["vip","10.100.0.11"]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.