-
Notifications
You must be signed in to change notification settings - Fork 9.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The show
command should warn, not fail, if the plan is stale.
#30269
Comments
Hi @nl-brett-stime, thanks for submitting this. There's some related work happening in #30205, fixing #30195, and I believe that what you're describing here may already be fixed in the 1.1 series. Could you check if 1.1.2 resolves the issue for you? |
Shouldn't that be #28136 seems like another duplicate that might be fixed, which is excellent (and my CI/CD scripts have been experiencing this stale plan warning for a few years - there's no good way to get at the JSON for an applied plan otherwise - so I'm really happy about this potential fix) |
Ah, yes, thanks for the correction! I've just verified that this is fixed in Terraform 1.1.3, so I'm closing this and the other issue accordingly. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Sometimes it's useful to see what the changes related to a give plan were even after it's been applied. When using the
show
command on a stale plan, ideally Terraform would report a warning and continue to show the plan instead of reporting an error and terminating. Alternately, maybe add an option to ignore staleness. E.g.,terraform show -ignore-stale -json some.tfplan
Terraform Version
Tested in
v1.0.11
but probably applies to more recent versions as well.Terraform Configuration Files
Any config
Debug Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform init
terraform plan -out some.tfplan
terraform apply some.tfplan
terraform show -json some.tfplan
Additional Context
References
The text was updated successfully, but these errors were encountered: