It's too easy to inherit unexpected config values
Bug #720213 reported by
Julian Edwards
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
| lazr.config |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Deleting a config item in a child schema doesn't necessarily have the intended effect if it's also defined in the schema that it extends. This aspect also makes it somewhat difficult to test production config changes and can have dangerous consequences. The inheritance model also makes it extremely hard to visualize the end configuration without specialized tools to do so, particularly in the case of multiple and multi-level inheritance.
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in lazr.config: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| Changed in lazr.config: | |
| importance: | High → Low |
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
One suggested solution is to have an <include> rather than an <extend> mechanism.