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
terraform-provider-aws_v3.47.0_x5 plugin - interface {} is nil, not *aws.AWSClient #20015
Comments
Temporary solution:
It should destroy most or every of your resource. And restore TF state which does not trigger error. |
@ewbankkit Is there some plans to fix this bug? |
Still happening on 3.48.0
The above was when attempting to do a destroy of all the resources, prior to this there was the following
|
Hi @Erucolindo96 👋 Terraform |
@justinretzolk I had the same issue, upgrading to v1.0.9 worked for me |
We've seen a few other similar issues that were resolved by Terraform v1.0.9 as we'd expected. Given that's the case, I'm going to close this issue out as well. If you feel I've done this in error, please do let us know. |
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. |
Community Note
Terraform CLI and Terraform AWS Provider Version
OS: Ubuntu 18.04, but on Windows there are same effect
Affected Resource(s)
Terraform Configuration Files
terraform { backend "s3" { bucket = "bucket_name" key = "local/terraform.tfstate" region = "eu-central-1" dynamodb_table = "table_name" } }
Debug Output
Panic Output
Output at terraform destroy (only plan were executed, even no asking for confirmation to delete resources, crash before them)
Expected Behavior
Display confirmation to delete resource's, and delete them after that
Actual Behavior
Crash before asking for confirmation to delete resource's
Steps to Reproduce
After that i can replace it every time when i do:
Important Factoids
This issue not depends on TF version - tested with TF 1.0.0, 1.0.1 and 0.15.5 - same effect.
References
Something similar were reported in previous time:
#8681
#7772
https://discuss.hashicorp.com/t/terraform-aws-provider-panic-plugin-did-not-respond/23396
The text was updated successfully, but these errors were encountered: