Fix hardcoded availability zone issues (VPC-WOR) #14500
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Community Note
Relates #12995
Release note for CHANGELOG:
This PR takes on 3 tasks:
resource_aws_vpc_dhcp_options_test
resource_aws_vpc_endpoint_connection_notification_test
resource_aws_vpc_endpoint_service_allowed_principal_test
resource_aws_vpn_gateway_test
.resource_aws_vpc_dhcp_options_test
resource_aws_vpc_endpoint_connection_notification_test
resource_aws_vpc_endpoint_service_allowed_principal_test
resource_aws_vpn_gateway_test
.testAccAvailableAZsNoOptInConfig()
(defined inresource_aws_instance_test
) to cut down on repetitive boilerplate of data sourcedata "aws_availability_zones" "available"
.The output from acceptance testing in AWS Commercial:
The output from acceptance testing in AWS GovCloud (US):
+ Originally failed on TC but fixed after