Title: Keep approval on retry when the plan hasn’t changed
Issue: Retrying a failed run creates a new run that needs approval again, even when nothing changed in the code. An approval policy can’t solve this. The retry’s policy input has nothing that links it to the original run or its approval, and it looks the same as a manual Trigger.
Approving just because it’s the same commit isn’t safe either. If part of the apply went through, the retry’s plan can be different from the one that was approved.
Proposal: keep the approval if the retry’s plan matches the approved plan, or add the original run ID to the policy input (like run.retry_of) so customers can write the rule themselves.
Log in to comment and vote
Comments1
Gray Crater
Oct 19
Adding more details so it’s clearer:
Title: Keep approval on retry when the plan hasn’t changed
Issue: Retrying a failed run creates a new run that needs approval again, even when nothing changed in the code.
An approval policy can’t solve this. The retry’s policy input has nothing that links it to the original run or its approval, and it looks the same as a manual Trigger.
Approving just because it’s the same commit isn’t safe either. If part of the apply went through, the retry’s plan can be different from the one that was approved.
Proposal: keep the approval if the retry’s plan matches the approved plan, or add the original run ID to the policy input (like
run.retry_of) so customers can write the rule themselves.