-
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
[Version 2 Release] resource/aws_route53_zone: Remove deprecated top-level vpc_id and vpc_region arguments #7693
Comments
Pull request submitted: #7695 |
…guments Reference: #7693 Output from acceptance testing: ``` --- PASS: TestAccAWSRoute53Zone_basic (46.72s) --- PASS: TestAccAWSRoute53Zone_Comment (65.30s) --- PASS: TestAccAWSRoute53Zone_DelegationSetID (53.41s) --- PASS: TestAccAWSRoute53Zone_ForceDestroy (184.65s) --- PASS: TestAccAWSRoute53Zone_ForceDestroy_TrailingPeriod (184.40s) --- PASS: TestAccAWSRoute53Zone_multiple (61.31s) --- PASS: TestAccAWSRoute53Zone_Tags (62.64s) --- PASS: TestAccAWSRoute53Zone_VPC_Multiple (102.63s) --- PASS: TestAccAWSRoute53Zone_VPC_Single (57.30s) --- PASS: TestAccAWSRoute53Zone_VPC_Updates (176.68s) --- PASS: TestAccAWSRoute53ZoneAssociation_basic (97.35s) --- PASS: TestAccAWSRoute53ZoneAssociation_region (121.29s) --- PASS: TestAccDataSourceAwsRoute53Zone (79.95s) ```
Unfortunately,
association with another vpc will be initially created, removed with next apply, then created again and so on.
|
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! |
Description
Tracking issue for https://www.terraform.io/docs/providers/aws/guides/version-2-upgrade.html#resource-aws_route53_zone
vpc_id and vpc_region Argument Removal
Switch your Terraform configuration to
vpc
configuration block(s) instead.For example, given this previous configuration:
An updated configuration:
The text was updated successfully, but these errors were encountered: