-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
[v0.12.6] provider.aws v3.1.0 still shows "Invalid resource instance data in state" #25827
Comments
Hi! Thanks for reporting this. Based on the error report you showed, I think this is probably a valid issue, and I'd like to reproduce it locally. To do that, I have to be able to run this and run it on my workstation without inventing any details in order to be confident we're seeing the same behavior. As-is, I don't have your vars, so I'd have to invent some details. Can you please restate your reproduction case such that I can copy-paste it and run it locally? If it's easier to provide via a github repo rather than a copy-paste, you're welcome to make a PR against https://github.com/danieldreier/terraform-issue-reproductions to share it, or provide your own GH repo. |
Hi! I can try but I believe the issue isn't with the variables but with the state itself. In any case, here's the variables.tf and terraform.tfvars file:
|
I'm also hitting this error (with Terraform 0.13.0). In my case it is complaining because my state file contains the obsolete API gateway attribute "request_parameters_in_json". |
Editing the state file and removing the unsupported attributes helped me.
|
Scary but it works 😨 |
👋 Hi! This is a duplicate of #25752 - this issue will be fixed in the next terraform release. Thanks! |
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
Note: seems like it might still be happening with Terraform v0.13.0? hashicorp/terraform-provider-aws#14431 (comment)
Terraform Configuration Files
Note: redacted for privacy purposes
Debug Output
Need to review and scrub before posting
Crash Output
Expected Behavior
The plan to work. It should have replaced the instance because of a new variable. Interestingly enough, if I run just
terraform plan
instead of using-target=
the plan outputs properly. Since these aws_instances are being replaced, I'd rather not take down the entire group of them all at once, hence the-target=
flag.Actual Behavior
Got an error similar to hashicorp/terraform-provider-aws#14431
Steps to Reproduce
Additional Context
References
Was told by this comment to log an issue if it's still happening with Terraform v0.12.X (which I am on). hashicorp/terraform-provider-aws#14431 (comment)
The text was updated successfully, but these errors were encountered: