Canonical Juju

allow charms to decline config changes

Bug #1948969 reported by Simon Déziel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Wishlist
Unassigned

Bug Description

Some configuration changes are not always possible after the initial deployment.

For example, when deploying LXD, one has to decide if standalone or cluster mode is to be used and once set, this cannot be undone. Similarly, the charm accepts a LXD preseed which makes no sense to alter once a unit is deployed.

It would be handy if the charm could simply reject change attempts on certain config keys. Maybe some kind of "modifiable: false" attribute?

Simon Déziel (sdeziel)
tags: added: lxd-cloud
Revision history for this message
Stéphane Graber (stgraber) wrote :

In discussions with the Juju team, it was mentioned that a few of the potential options for this would be:
 - Separate config validation hook
 - Stronger typing of the config to allow for schema validation
 - Supporting attaching scripts (LUA or the like) to a charm's config which would then be run by the controller to validate the user's config

Revision history for this message
John A Meinel (jameinel) wrote :

We are looking to add a few ways to do config validation, one of the ideas is around scriptlets (being able to run validation code inside the juju server in a sandboxed form).
Charms can certainly ignore/set Blocked for a config-changed value, but it doesn't help from the user then seeing 'juju config app' and still seeing the invalid value.

Changed in juju:
importance: Undecided → Wishlist
status: New → Triaged
tags: added: scriptlets
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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