-
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
Closes #10921 #11078
Closes #10921 #11078
Conversation
Thanks for the PR, @thatderek. Normally we prefer separate PRs for separate features, but the changes are small enough that the two changes are easy to review. The errors are because AWS has added a new AZ in For future reference, the data "aws_region" "current" {}
locals {
region_blacklisted_az_ids = {
"us-west-2" = ["usw2-az4"]
}
blacklisted_az_ids = lookup(local.region_blacklisted_az_ids, data.aws_region.current.name, [])
}
data "aws_availability_zones" "available" {
state = "available"
blacklisted_zone_ids = local.blacklisted_az_ids
}
resource "aws_subnet" "main" {
vpc_id = "${aws_vpc.main.id}"
...
availability_zone = data.aws_availability_zones.available.names[0]
} I'll update the test code to use that snippet so that all the tests will pass cleanly. |
Ohhhhh @gdavison that makes sense. I figured the test happened to already be compatible with whatever subset of AZs AWS had allocated to the account Hashicorp's test-runners. Got it. I will study this more carefully in the future. On the number of items, no problem. I figured I'd knock it out since I was in the weeds anyhow, but I understand the preference. I'll separate them out in the future. ╭(◔ ◡ ◔)/ |
This has been released in version 2.41.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. 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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #10921
Relates #10688
Release note for CHANGELOG:
Output from acceptance testing:
Note: I tested in us-east-1 because of a mismatch in us-west-2 AZ's in my account and the available compute instance types. Specifically, when I tried us-west-2, I saw all sorts of these types of errors like:
I assume ☝️ should not affect this PR's acceptance. Also, I ran the larger suite of
aws_emr_cluster
tests because I also changed the tagging in accordance with #10688ʕ •ᴥ•ʔ