Feature Request P2
Status Update
Comments
md...@google.com <md...@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
[Deleted User] <[Deleted User]> #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?
md...@google.com <md...@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.
fe...@gmail.com <fe...@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)
Description
Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.
What you would like to accomplish:
My team uses Google Analytics extensively and manages more than 4,000 separate Google Analytics accounts for our clients. Since we manage such a huge volume of accounts, we explore and implement ways we can automate work across these accounts if we need to make mass changes.
Since we do make changes en masse, it would be absolutely fantastic if we could also make annotations of these changes, including error logs if for whatever reason we tried, for example to add a filter but wasn't able to due to our lack of permissions.
How this might work:
I can see this working like any of the other actions through the API. Take for example adding filters, you have the following methods available: delete, get, insert, list, patch and update. I can see adding annotations in a similar way with the following methods: list and insert.
To my knowledge annotations don't really have ID's tied to them, but if it's possible to get or search for an annotation with a specific string inside the message, we could use that to delete, update or patch existing annotations.
If applicable, reasons why alternative solutions are not sufficient:
Other information (workarounds you have tried, documentation consulted, etc):
We've tried utilizing Python Selenium automations to add annotations en masse, but we constantly have issues with the login screen when we have the bot initially access the accounts. I understand this is due to security concerns, so if we could at least accomplish this through the API that already has built in security measures, we can be effective with our work.