Feature Request: Add charm config metadata to disable post deploy config modification

[james beedy]

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!

[Richard Harding (rharding)]

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
https://jaas.ai/docs/disabling-commands

and we have the ability to have read-only users on a model
https://jaas.ai/docs/user-types-and-abilities

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?

[james beedy (jamesbeedy)]

"Is the desire to let them still deploy, add-unit, etc that a write user could do but only not change config?" - yes

Here is an example of what I have in mind:

options:
  config-charm-author-doesnt-want-user-to-be-able-to-modify-post-deploy:
    post-deploy-enabled: false
    default: ""
    type: string
    description: |
      This configuration option is locked from being changed after the charm is deployed
      because post-deploy-enabled: false.

Something along these lines might help charm authors more formally lock down what charm config options can't be modified after a charm has been deployed.

[Richard Harding (rharding)]

Ok, this falls under a long standing goal of adding a richer schema to config to enable things like this. Thanks.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.