Rudder

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)

What 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