Assigned
Status Update
Comments
wi...@google.com <wi...@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
ca...@gmail.com <ca...@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?
wi...@google.com <wi...@google.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.
ca...@gmail.com <ca...@gmail.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)
al...@bonfireleads.com <al...@bonfireleads.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
ca...@gmail.com <ca...@gmail.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
di...@groupbyinc.com <di...@groupbyinc.com> #8
Any progress in here?
Description
What you would like to accomplish: Stop any further spend on the account once a limit is reached.
How this might work: Allow setting a daily and/or monthly spend limit in billing. When/if this limit is reached, stop any more spend happening.
This is to protect against a security breach or inefficient process which could cause a big spend in a short space of time.
If applicable, reasons why alternative solutions are not sufficient: Alerts are not enough. Bug spend could happen in a very short space of time, meaning it's not feasible to act on an alert quick enough.
Other information (workarounds you have tried, documentation consulted, etc): There are no alternatives available.