Assigned
Status Update
Comments
mo...@google.com <mo...@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
br...@gmail.com <br...@gmail.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?
se...@gmail.com <se...@gmail.com> #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.
ni...@enplore.com <ni...@enplore.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)
[Deleted User] <[Deleted User]> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
ae...@google.com <ae...@google.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
ga...@gmail.com <ga...@gmail.com> #8
Any progress in here?
[Deleted User] <[Deleted User]> #9
I would like this feature as well.
[Deleted User] <[Deleted User]> #10
Hello, any progress in here? Please is very frustrating.
[Deleted User] <[Deleted User]> #11
Hi, open request for more than 3 years for a simple change. Please proceed that.
al...@gmail.com <al...@gmail.com> #12
+1. :(
er...@findme.com.ph <er...@findme.com.ph> #13
We need this.
gr...@gmail.com <gr...@gmail.com> #14
please add this!
ar...@airbus.com <ar...@airbus.com> #15
+1 !
jo...@dirxion.com <jo...@dirxion.com> #16
+1
is...@google.com <is...@google.com>
[Deleted User] <[Deleted User]> #17
+1
jo...@voa.cloud <jo...@voa.cloud> #18
We need this please
[Deleted User] <[Deleted User]> #19
+1
mu...@gmail.com <mu...@gmail.com> #20
+1
2018 =(
2018 =(
ra...@gmail.com <ra...@gmail.com> #21
+1
ma...@gmail.com <ma...@gmail.com> #22
+1
sa...@connectedjourneys.co.nz <sa...@connectedjourneys.co.nz> #23
+1
ad...@resolute.com <ad...@resolute.com> #24
+1
[Deleted User] <[Deleted User]> #25
+1 (again) coming up to 5 years?
bf...@gmail.com <bf...@gmail.com> #26
+1
st...@gmail.com <st...@gmail.com> #27
+1
hs...@gmail.com <hs...@gmail.com> #28
+1
[Deleted User] <[Deleted User]> #29
+1
al...@gmail.com <al...@gmail.com> #30
+1
vi...@cloud66.com <vi...@cloud66.com> #31
+1
we...@gmail.com <we...@gmail.com> #32
+1
cr...@gmail.com <cr...@gmail.com> #33
Please implement this
[Deleted User] <[Deleted User]> #34
+1
pe...@paymentsense.com <pe...@paymentsense.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.
sa...@cvshealth.com <sa...@cvshealth.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
el...@gmail.com <el...@gmail.com> #37
+1
[Deleted User] <[Deleted User]> #38
+1
ma...@acciona.com <ma...@acciona.com> #39
+1
ls...@paloaltonetworks.com <ls...@paloaltonetworks.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
wl...@gmail.com <wl...@gmail.com> #41
+1
[Deleted User] <[Deleted User]> #42
+1
ma...@casble.com <ma...@casble.com> #43
+1
[Deleted User] <[Deleted User]> #44
+1
br...@getlucro.com <br...@getlucro.com> #45
+1 (same goes for description). Should update in-place
g....@linqhost.nl <g....@linqhost.nl> #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.
[Deleted User] <[Deleted User]> #47
+1
ki...@google.com <ki...@google.com> #48
+1
[Deleted User] <[Deleted User]> #49
Guys, this feature was requested in 2014, what's the problem? Why hasn't this been implemented or at least an update been given??
yo...@ipaymu.com <yo...@ipaymu.com> #50
+1
Whe the ETA for this simple important request?
Whe the ETA for this simple important request?
gr...@gmail.com <gr...@gmail.com> #51
At least say NO so we are not left hanging for years and years. If you are looking for a reason why Google you can't compete with Azure and AWS this thread would be a prime example. If Google can't respond to basic feature requests then it is easy to imagine they can't do other basic things. Did Elon Musk take over Google too? Are 1/2 of you Google employees fired or just too busy checking out Amazon prime deals working at home? WTF, crickets for 8+ years? Do Something!
ma...@gmail.com <ma...@gmail.com> #52
+1
ce...@parquery.com <ce...@parquery.com> #53
+1
bo...@google.com <bo...@google.com>
bo...@google.com <bo...@google.com> #54
Hello,
Thanks for reaching out to us!
The Feature Request has been created and the Product Engineering Team is working on this request. At this moment, there is no ETA to this request. Thank you for your trust and continued support to improve Google Cloud Platform products.
In case you want to report a new issue, please do not hesitate to create a new
ma...@google.com <ma...@google.com>
fo...@bladefs.com <fo...@bladefs.com> #55
+1, this would be a very valuable feature.
Description
For example, you may have reserved a static ip address to use as your production ip for your web server, and names it "Production Web IP". Then later on the use of that server may change, and it is no longer used as your production web server, but you need to keep the same IP address (maybe it is registered with some external service as an allowed origin for some service that you will still be using.
In this case you will end up with a Static IP Address called "Production Web IP", that is not what is says it is. Whilst functionally it will work fine, it may become confusing for the purpose of administration in the future.
Therefore it would be useful to be able to rename that static ip address, for example:
gcutil setaddress "Production Web IP" --new_name "SMS Server"