Allow renaming VPCs and modifying subnets' description [110776122]

Assigned

Feature Request

Status Update

No update yet.

Description

lb...@google.com

created issue #1

Jun 25, 2018 02:42PM

We would like to be able to rename a VPC after it was created to comply to the naming convention instead of recreating the resource from scratch.

Comments

lb...@google.com <lb...@google.com> #2Jun 25, 2018 02:53PM

To solve this problem, create the two routes with different priorities, like this:

Route1: Destination:0.0.0.0/0<-------> Next hop: ILB(IN us-east1) <------> Priority:950

Route2: Destination:0.0.0.0/0<-------> Next Hop: ILB(IN us-west1) <------> Priority:951

As long as the forwarding rules aren't configured to be globally accessible, the next hops are regional. That is:

From the perspective of us-west1, this route is available:

Route2: Destination:0.0.0.0/0<-------> Next Hop: ILB(IN us-west1) <------> Priority:951

From the perspective of us-east1, this one is available:

Route1: Destination:0.0.0.0/0<-------> Next hop: ILB(IN us-east1) <------> Priority:950

It doesn't matter that these have different priorities in the route table because only one is "active" in each region (as long as global access isn't configured).

fa...@google.com <fa...@google.com> #3Jun 25, 2018 07:54PM

Assigned to gc...@google.com.

Thank you for helping us improve the functionality of our products. I forwarded your feature request and suggestions to the product team. You can track this thread for any updates, or post additional comments about the request. However, we cannot provide an ETA or guarantee its implementation at this point in time.

se...@myrepublic.net <se...@myrepublic.net> #4Feb 13, 2019 07:19AM

We're also impacted by this.

Please add the possibility to rename.
It's really not understandable how simple things like changing a name can't be done.

ha...@sap.com <ha...@sap.com> #5Aug 14, 2019 09:34AM

Hello Colleagues ,
We also affected by this . Kindly check on this with priority and let us know when the feature will be done .
We see on all other Clouds , feature of rename on vpc subnets is available and we can do it without much efforts .
Thanks ,
Harirpasath.N

ha...@sap.com <ha...@sap.com> #6Aug 14, 2019 09:47AM

Hello google colleagues ,

Kindly let us know , what is the ETA for this request , as this issue is open since 2018 .

Thanks ,
Hariprasath.N

br...@brettjones.com <br...@brettjones.com> #7Dec 5, 2019 07:32PM

+1 here. Renaming VPCs and subnets should be possible without deconstructing and rebuilding networks, a process which may involve multiple other parties.

br...@cannonballtrading.com <br...@cannonballtrading.com> #8Dec 5, 2019 07:47PM

+1 here. Renaming VPCs and subnets should be possible without deconstructing and rebuilding networks, a process which may involve multiple other parties.

kt...@google.com <kt...@google.com> #9Sep 2, 2021 08:59PM

Hello everyone,

Thank you for your ongoing patience. We know it's been a while since you don't hear back from us.

Be sure that we hear you, all new reports are being shared with the Product team. The Cloud VPC Engineering team is still working on this issue to provide a resolution.

Further updates, including a possible ETA will be posted in this thread.

to...@maxedadiygroup.com <to...@maxedadiygroup.com> #10Nov 7, 2022 07:14AM

+1 here. Is not a nice to have feature; it is a should have functionality.

Thanks & regards, Tom

ro...@softchoice.com <ro...@softchoice.com> #11Dec 2, 2022 06:22PM

this one is still open from 2018. I really can use this feature with my customer to properly follow the naming convention. when is the ETA?

pi...@gmail.com <pi...@gmail.com> #12Feb 4, 2023 12:21AM

any movement here? The ability to have well defined naming convention is the key in the cloud. It's obvious and this feature should be implemented.

cc...@proveedorexterno.com <cc...@proveedorexterno.com> #13Feb 16, 2023 10:41AM

any updates on this??

gu...@ig.com <gu...@ig.com> #14Mar 27, 2023 03:16PM

+1 from me, would be good to be able to rename without destroying

ch...@rewe-group.com <ch...@rewe-group.com> #15Mar 28, 2023 03:05PM

We would also like to know if there is any progress on this case. Can you provide an ETA ?
As said before, naming ressources is a key and we would like to change descriptions without rebuilding everything

Best Regards
Chris

lu...@engdb.com.br <lu...@engdb.com.br> #16Sep 27, 2023 08:54PM

+1 from me, deploying a brand new network just to change its name doesn't make sense. We believe it has to be a "should have" functionality.

iv...@ultimatesoftware.com <iv...@ultimatesoftware.com> #17Feb 9, 2024 01:32PM

Bump