Assigned
Status Update
No update yet.
Comments
gh...@google.com
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
av...@gmail.com
Comment has been deleted.
la...@kinsta.com
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.
gh...@google.com
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)
la...@kinsta.com
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
Description
It would be very useful having an option to tune some of the Cloud API endpoints' rate limiting. I'm especially looking for an option to limit the Compute Engine VM / Snapshot - delete action - limit. Being able to set a 2/day limit would be very great.
In some cases, it would be even better if we could adjust this rate limit on a per IAM user level.
We have thousands of VMs and tens of thousands of snapshots (99% scheduled) which we constantly run and very rarely dismantle "manually". Having a rate limit on a particularly sensitive endpoint can streamline our workflow a lot.
Right now we only provide this permission temporarily, though in case the IAM admin's account is compromised (we're following all best practices, but it is still an option, even if the likelihood is very low), but with the rate limit, even in case of a compromise the deletion is limited.
Thanks