-
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
provider/aws: aws_vpc operations fail in v0.6.10 #4874
Comments
Thanks for the report, @laggyluke. We're investigating this now. |
… support it - use eu-central-1 to a config to check for #4874 - update documentation
#4879 should fix this, we're double checking things, thanks! |
We merged #4897, thanks for the report! We're going to close this for now, let us know if you need anything else. |
Thanks a lot for your work! |
… support it - use eu-central-1 to a config to check for hashicorp#4874 - update documentation
… support it - use eu-central-1 to a config to check for hashicorp#4874 - update documentation
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. |
Possibly related to #3994, might be due to
eu-central-1
region not supporting VPC ClassicLink or something like that.Configuration:
Plan:
Apply:
Refresh:
The configuration above works fine on v0.6.9.
The text was updated successfully, but these errors were encountered: