google_compute_public_advertised_prefix update step once PTR record is created

[acharrett]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to a user, that user is claiming responsibility for the issue.
• Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

In the process for provisioning a GCP BYOIP Public Advertised Prefix there is a step where you have to create a DNS record to validate that you own the IP block in question (see #18171 for retrieving the information required to create that DNS record).

Once that DNS record has been created there is a step to go back to the GCP API and inform it that the DNS record is available to to be validated.

WIth the CLI, this looks like gcloud compute public-advertised-prefixes update PAP_NAME --status=PTR-CONFIGURED

It would be great to have terraform native way to do this, rather than shell out to gcloud.

New or Affected Resource(s)

• google_compute_public_advertised_prefix

Potential Terraform Configuration

References

https://cloud.google.com/vpc/docs/create-pap#validate-ptr

b/341734977

[melinath]

Note from triage: This would likely require adding support for the status field.