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 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
Add the reserved-internal-range option to google_compute_subnetwork to support using an ip_cidr from google_network_connectivity_internal_range.
This would allow a subnet to be created with a automatically assigned subnet from the target_cidr_range by prefix_length
caveman8fb
changed the title
Add support for reserved internal ranges to VCP Subnets
Add support for reserved internal ranges to google_compute_subnetworkJun 20, 2024
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
Add the
reserved-internal-range
option togoogle_compute_subnetwork
to support using an ip_cidr fromgoogle_network_connectivity_internal_range
.This would allow a subnet to be created with a automatically assigned subnet from the
target_cidr_range
byprefix_length
New or Affected Resource(s)
google_compute_subnetwork
Potential Terraform Configuration
References
https://cloud.google.com/vpc/docs/create-use-internal-ranges#create-subnet-partial-range
The text was updated successfully, but these errors were encountered: