---
title: "Comment by Rishabh Mishra on \"Deploying Terraform to AWS with GitHub Actions and OIDC\" | Hashnode"
description: "The saved-plan rule is the part I would keep. Applying exactly what was reviewed removes a whole class of surprises. I would also keep each plan artifact tied t"
url: "https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834/comment/6ae55a2cc682f92fba631f50"
---

[Discussion](https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834)

Comment [Deploying Terraform to AWS with GitHub Actions and OIDC](https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834)

[Rishabh Mishra](https://hashnode.com/@rushdeploy)

[Oct 31](https://hashnode.com/posts/deploying-terraform-to-aws-with-github-actions-and-oidc/6ae4f89cd1f5980215892834/comment/6ae55a2cc682f92fba631f50)

The saved-plan rule is the part I would keep. Applying exactly what was reviewed removes a whole class of surprises. I would also keep each plan artifact tied to its run, so a re-run cannot quietly apply a newer change.
