-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
panic when applying a saved plan file created with "terraform plan -destroy -out=tfplan" #19149
Comments
I have re-confirmed this with v0.12.0-alpha4. Some more details, this time. This can be reproduced with any resource type, but I did it this time using the following configuration: resource "null_resource" "blah" {
} After running
So far so good. But then applying that saved plan causes the same panic as before:
Running just
Therefore it seems most likely that this is a bug in the plan file decoder where it's not properly rebuilding the internal |
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Terraform Version
Crash Output
Expected Behavior
The AWS provider should have deleted the instances as planned.
Actual Behavior
The provider (most likely: the shared provider SDK) seems to have triggered a panic during the decoding of the provider request to apply the change.
Steps to Reproduce
With resources already existing from a previous apply:
terraform plan -destroy -out=tfplan
terraform apply tfplan
The text was updated successfully, but these errors were encountered: