Feature Request: Add charm config metadata to disable post deploy config modification
Bug #1855464 reported by
james beedy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
As a charm author, sometimes I wish to disable charm config from being modified post deploy by the user deploying the charm. Could we add some metadata element to the charm config schema that an author could set to disable/enable the post deploy modification of the charm config?
Thanks!
To post a comment you must log in.
Can you let us know what you're looking for in a bit more detail?
We have the ability to disable commands that can change the model /jaas.ai/ docs/disabling- commands
https:/
and we have the ability to have read-only users on a model /jaas.ai/ docs/user- types-and- abilities
https:/
Is the desire to let them still deploy, add-unit, etc that a write user could do but only not change config? Can you describe the use case a bit more please?