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
Changing ip_cidr_range argument of google_compute_subnetwork resource leads to recreation of the subnetwork object, the update method is not implemented.
GCE API has a method Subnetworks: expandIpCidrRange [1] that allows to modify the existing subnetwork and change a CIDR range in case if a new CIDR range is a superset of the range previously defined before the update.
The proposal is to modify google_compute_subnetwork resource by adding code allowing to expand a CIDR range. It's not clear to me how resource should behave in a new CIDR range is not a superset of an old one.
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.
ghost
locked and limited conversation to collaborators
Apr 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
0.8.5
Affected Resource(s)
Changing ip_cidr_range argument of google_compute_subnetwork resource leads to recreation of the subnetwork object, the update method is not implemented.
GCE API has a method Subnetworks: expandIpCidrRange [1] that allows to modify the existing subnetwork and change a CIDR range in case if a new CIDR range is a superset of the range previously defined before the update.
The proposal is to modify google_compute_subnetwork resource by adding code allowing to expand a CIDR range. It's not clear to me how resource should behave in a new CIDR range is not a superset of an old one.
[1] - https://cloud.google.com/compute/docs/reference/latest/subnetworks/expandIpCidrRange
The text was updated successfully, but these errors were encountered: