resource/aws_route53_zone: Support multiple vpc associations, deprecate vpc_id and vpc_region, and enhance acceptance testing #6299
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.
Route53 Hosted Zones can have multiple VPC associations. Previously, the resource would error when attempting to import a zone with multiple associations. I wasn't planning on this large refactoring but trying to get the other changes in highlighted the need to bring this resource up to more current practices.
Closes #892
Closes #5317
Closes #5736
Changes:
vpc
TypeSet attribute to support exclusive management and import of multiple VPC associationsvpc_id
andvpc_region
attributes in favor ofvpc
, adding note to Version 2 Upgrade GuideOutput from acceptance testing: