Clarification of Policy Backwards-Compatiblity
Hey!
We’ve clarified in our documentation our approach to policy backwards-compatibility.
With this in mind, we’ll be introducing a new feature soon (18th September) - approval policy evaluation for proposed runs whose plan policies signal a warning. Proposed runs that result in a plan policy warning will now go into the PENDING_REVIEW state if there is any approval policy attached, and wait in this state for approval. This will let you set up flows where proposed runs will only be marked as successfully finished (and e.g. unblock related pull requests) when all interested stakeholders have signed off on them.
This means that you should make sure your approval policies are able to handle such a new state, as is shown in the new documentation section.