-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Module Issues w/ Terraform v0.13.0 #974
Comments
I think this is an aws provider v3 issue: Can you try again but lock your AWS provider to version 2? e.g.
|
Oops. The |
Thanks @dpiddockcmp I am sure that tainting these resources would have been the more elegant solution. But I just went ahead and manually edited the .tfstate, removing this attribute. |
It looks like this might be a bungled schema update. Normally the provider should handle migrations like this. Hopefully it will get automatically fixed for other users in TF 0.13.1: hashicorp/terraform#25779 |
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. |
After upgrading to Terraform v0.13.0, the module errors out with refresh/plan/apply.
tf init
tf init -reconfigure
I'm submitting a...
What is the current behavior?
On tf refresh/plan/apply, I get the following error for each worker:
From tfstate:
The text was updated successfully, but these errors were encountered: