Immutable config items
Bug #1064980 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I have a couple of charms where changing certain config after its initially been set is very bad; specifically ceph and hadoop where parts of the config are used to create keys/filesystem identifiers.
Although its possible to ignore such config changes in existing service units (and potentially error the config-changed hook to indicate something bad was done) any new service units added to existing services where this has happened will pickup the new value.
Result: undefined or really bad behaviour.
It would be nice if a config element could be declared immutable so that once its been set, it can't be changed.
| description: | updated |
Revision history for this message
| Clint Byrum (clint-fewbar) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in juju: | |
| importance: | Medium → Low |
To post a comment you must log in.
Great idea. I have seen this use case as well.