You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came out of the cg-provision meeting on May 21st
Our cg-provision pipeline (also aws-broker and maybe others) is configured to run terraform plan, and in a later job run terraform apply. However, that apply doesn't make use of a saved plan file. This means infrastructure drift during plan review and before the apply job is triggered can result in unexpected and possibly destructive changes.
Instead, we should save the plan output from the terraform plan job and make use of it in the apply job.
This came out of the cg-provision meeting on May 21st
Our
cg-provision
pipeline (alsoaws-broker
and maybe others) is configured to runterraform plan
, and in a later job runterraform apply
. However, thatapply
doesn't make use of a saved plan file. This means infrastructure drift during plan review and before the apply job is triggered can result in unexpected and possibly destructive changes.Instead, we should save the plan output from the
terraform plan
job and make use of it in the apply job.options:
The text was updated successfully, but these errors were encountered: