Assigned
Status Update
Comments
fa...@google.com <fa...@google.com> #2
I have forwarded this request to the engineering team. We will update this issue with any progress updates and a resolution.
Best Regards,
Josh Moyer
Google Cloud Platform Support
Best Regards,
Josh Moyer
Google Cloud Platform Support
fa...@google.com <fa...@google.com> #3
This is not only useful for IP addresses, but also for many other resources. I understand that names are currently used as identifiers, so this request is probably not trivial to implement. Maybe distinguishing between a (numeric, automatically generated) identifier and a (textual) label is the way to go?
an...@stanford.edu <an...@stanford.edu> #4
Is it any hope? We have migrated our IP address to the server with different role, and now the name of this IP address resource doesn't match its role at all. It seems to be trivial enough to momentary reserve static IP address of the old named resource, drop resource, and immediately recreate it with the new name and the old IP address.
fa...@google.com <fa...@google.com>
jo...@sony.com <jo...@sony.com> #5
This would also improve life when using the Google Deployment Manager (since it otherwise error's out if you've changed a name of an IP)
d....@i2tic.com <d....@i2tic.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
re...@gmail.com <re...@gmail.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
do...@gmail.com <do...@gmail.com> #8
Any progress in here?
jo...@gmail.com <jo...@gmail.com> #9
I would like this feature as well.
[Deleted User] <[Deleted User]> #10
Hello, any progress in here? Please is very frustrating.
ma...@gmail.com <ma...@gmail.com> #11
Hi, open request for more than 3 years for a simple change. Please proceed that.
la...@gmail.com <la...@gmail.com> #12
+1. :(
st...@gmail.com <st...@gmail.com> #13
We need this.
oh...@gmail.com <oh...@gmail.com> #14
please add this!
jo...@shutterstock.com <jo...@shutterstock.com> #15
+1 !
te...@google.com <te...@google.com> #16
+1
[Deleted User] <[Deleted User]> #17
+1
no...@homedepot.com <no...@homedepot.com> #18
We need this please
re...@gmail.com <re...@gmail.com> #19
+1
jl...@allyy.io <jl...@allyy.io> #20
+1
2018 =(
2018 =(
se...@erzz.com <se...@erzz.com> #21
+1
an...@gmail.com <an...@gmail.com> #22
+1
ry...@vandis.com <ry...@vandis.com> #23
+1
qb...@gmail.com <qb...@gmail.com> #24
+1
jo...@artlogic.net <jo...@artlogic.net> #25
+1 (again) coming up to 5 years?
ch...@phixflow.com <ch...@phixflow.com> #26
+1
ej...@gmail.com <ej...@gmail.com> #27
+1
[Deleted User] <[Deleted User]> #28
+1
vi...@victorworkshop.com <vi...@victorworkshop.com> #29
+1
th...@ottogroup.com <th...@ottogroup.com> #30
+1
we...@betterbridge.com <we...@betterbridge.com> #31
+1
eg...@envisageinternational.com <eg...@envisageinternational.com> #32
+1
Ja...@gtempaccount.com <Ja...@gtempaccount.com> #33
Please implement this
[Deleted User] <[Deleted User]> #34
+1
ji...@cloudtrucks.com <ji...@cloudtrucks.com> #35
+1, don't see why this would be hard. If the underlying GCP infrastructure depends on the name remaining unchanged, then the frontend can simply provide a way to alias it such that the end-user doesn't have to see the "original" name anymore.
th...@gmail.com <th...@gmail.com> #36
Bumping this.
Definitely useful feature at least provide a way to alias this.
+1
Definitely useful feature at least provide a way to alias this.
+1
ch...@gmail.com <ch...@gmail.com> #37
+1
me...@gmail.com <me...@gmail.com> #38
+1
ed...@gmail.com <ed...@gmail.com> #39
+1
iv...@gmail.com <iv...@gmail.com> #40
+1 Please add this feature
shouldn't be a very difficult implementation but benefits lots of people
shouldn't be a very difficult implementation but benefits lots of people
sc...@gmail.com <sc...@gmail.com> #41
+1
ma...@soapeople.com <ma...@soapeople.com> #42
+1
ch...@gmail.com <ch...@gmail.com> #43
+1
te...@gigrev.com <te...@gigrev.com> #44
+1
ro...@gmail.com <ro...@gmail.com> #45
+1 (same goes for description). Should update in-place
ni...@bmg.com <ni...@bmg.com> #46
+1 here too. But the problem is also with disks. We currently use part of hostname in the name. Sometimes a machine has to be renamed and it's not possible.
fe...@gmail.com <fe...@gmail.com> #47
+1
co...@brandonmevans.com <co...@brandonmevans.com> #48
+1
Description
People coming from enterprise environments want to secure access to their VMs without having to dump a huge list of every known Google IP block into their rules. I honestly can't tell my customers that GCP is just as secure as their own environments in a data center right now.