User story #1443
closed
When the PT lib is updated, mark PI attached to structurally modified PT as broken
Description
When a PT is updated along with a new revision of the policy template reference library, we have to mark Policy Instances as broken if they are based on that PT that have structural changes to let the user save them back with meaningful parameter value.
Ex: an optional variable becomes mandatory: PI without that variable are now in error and should not be deployed.
What is a structural modification ?- in policy.xml/tmls
- add/remove a tml
- add/remove policy.xml/tmls/tml/variables
- except adding an optional variable
- in policy.xml/tmls/tml/variables, modification of attributes:
- type
- multivalued becomes monovalued (the opposition is not a structural modification)
- updates in resources files (promises templates, config files, etc)
- for policy.xml, modification of attributes
- description
- display
- template
- for policy.xml/tmls, change order of tmls
- for policy.xml/tmls, modification of attributes:
- orderon
- dependon
- bundles
- for policy.xml/tmls/variables, modification of attributes:
- name
- description
- longdescription
- section
- precedence
Updated by Jonathan CLARKE over 13 years ago
- Subject changed from When the PT lib is updated, desactivate PT with structural modifications to When the PT lib is updated, mark PI attached to structurally modified PT as broken
Updated by Jonathan CLARKE over 13 years ago
- Target version deleted (
15)
Depriorising this user story as it's a bit of a corner case and seems it will take a lot of time for not a huge value.
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to Ideas (not version specific)
Updated by François ARMAND almost 10 years ago
- Status changed from New to Rejected
In Rudder 2.10 and up, the detection of updated version of Techniques has gotten far better. We now know when directive should be saved again, and it's done automatically, and error appears in the promise regeneration box when it's the case.
So it seems that most (or all) of that user story is implemented. I'm going to close it and let new ticket be created with more specific needs.