-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
r/aws_vpc_endpoint_service_private_dns_verification: new resource #37176
Conversation
Community NoteVoting for Prioritization
For Submitters
|
66f968c
to
b04f735
Compare
b04f735
to
c9ed42e
Compare
) | ||
return | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it makes sense to poll on PrivateDnsNameConfiguration.State
== "verified"
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because this requires some other DNS registration bits which may or may not use AWS Route53, my initial thinking was not to poll. Maybe it makes sense to add an optional argument (wait_for_verified_status
?) so users can opt-in to this behavior if desired?
I'll think on this one a bit more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Started implementing an optional wait_for_verification
argument, and realized this can share the finder from the aws_vpc_endpoint_service
resource. I have another WIP PR that migrates this resource to AWS SDK V2, which will make it usable for this purpose. I'm going to move this back into draft state and finish once that migration is complete.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added an optional wait_for_verification
argument.
19cfb11
to
6b49c7e
Compare
This can be embedded in framework resources which do not require custom read operations.
41abde1
to
a3f0b1a
Compare
This resource will allow practitioners to start the verification process for a VPC endpoint service private DNS name via Terraform. ```console % make testacc PKG=ec2 TESTS="TestAccVPCEndpointServicePrivateDNSVerification_" ==> Checking that code complies with gofmt requirements... TF_ACC=1 go1.22.2 test ./internal/service/ec2/... -v -count 1 -parallel 20 -run='TestAccVPCEndpointServicePrivateDNSVerification_' -timeout 360m --- PASS: TestAccVPCEndpointServicePrivateDNSVerification_basic (218.59s) --- PASS: TestAccVPCEndpointServicePrivateDNSVerification_waitForVerification (262.01s) PASS ok github.com/hashicorp/terraform-provider-aws/internal/service/ec2 267.248s ```
a3f0b1a
to
793b8e6
Compare
This functionality has been released in v5.51.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. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
This resource will allow practitioners to start the verification process for a VPC endpoint service private DNS name via Terraform.
Relations
Closes #37163
References
Output from Acceptance Testing