You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.
resource"google_compute_public_advertised_prefix""example" {
name="example.com"# must match https://www.ietf.org/rfc/rfc1035.txtdescription="Description goes here"ip_cidr_range="1.2.3.4/5"parent_prefix=google_compute_public_delegated_prefix.self_link# other fields, possibly...
}
I think there would also need to be data sources implemented to access this data, given that there are no resources in a typical CRUD sense for this API endpoint. E.g. the docs for the fingerprint field of a PAP say "To see the latest fingerprint, make a get() request to retrieve a PublicDelegatedPrefix.".
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
There is a feature that allows Bring Your Own IP (BYOIP) with VPCs 👉 https://cloud.google.com/vpc/docs/bring-your-own-ip
That guide describes how public advertised prefixes and public delegated prefixes are required to allow the IP(s) to be used, and those resources aren't implemented in the provider yet.
New or Affected Resource(s)
Potential Terraform Configuration
I'm unsure what the configuration would look like as the API documentation says this for both API endpoints:
But using the JSON from the insert method docs for publicAdvertisedPrefixes it might look something like:
I think there would also need to be data sources implemented to access this data, given that there are no resources in a typical CRUD sense for this API endpoint. E.g. the docs for the fingerprint field of a PAP say "To see the latest fingerprint, make a get() request to retrieve a PublicDelegatedPrefix.".
References
The text was updated successfully, but these errors were encountered: