-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
diffs didn't match error on T3 server after taint then apply #5719
Comments
I can confirm this behaviour, and some other teams at our organization as well. Full error:
|
The fix for this has been merged into master for the |
This has been released in version 1.37.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This issue was originally opened by @twellspring as hashicorp/terraform#18733. It was migrated here as a result of the provider split. The original body of the issue is below.
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/twellspring/151fe1e56e5bc1689d541614b758ae71
Crash Output
https://gist.github.com/twellspring/8e75fb2e32910182e0dcbd3e9ae18351
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform taint
terraform apply
Additional Context
References
The text was updated successfully, but these errors were encountered: