Assigned
Status Update
Comments
de...@cleardata.com <de...@cleardata.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
jo...@google.com <jo...@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?
jo...@google.com <jo...@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.
jo...@cleardata.com <jo...@cleardata.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)
ph...@sada.com <ph...@sada.com> #6
Over 3 years to get something as basic as renaming a static IP address. Any progress here?
ni...@sada.com <ni...@sada.com> #7
Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!
do...@boozt.com <do...@boozt.com> #8
Any progress in here?
at...@gmail.com <at...@gmail.com> #9
I would like this feature as well.
an...@squarepoint-capital.com <an...@squarepoint-capital.com> #10
Hello, any progress in here? Please is very frustrating.
se...@cplcloud.com <se...@cplcloud.com> #11
Hi, open request for more than 3 years for a simple change. Please proceed that.
Description
We have a billing account, and multiple sub-billing accounts. We are trying to setup individual billing exports for _some_ of our sub-billing accounts (to feed into a cost analysis tool). We'd like to send these exports to different datasets in a single project for analyzing that data.
Bigquery exports only allow you to choose a project (and dataset) that is linked to the billing account in question. The project we want to export data to is linked to the parent (master) billing account.
The cloud storage export doesn't have this restriction. We currently send billing exports from multiple sub-accounts to multiple buckets in a _single project_
What you expected to happen:
Allow billing exports to go to projects that aren't attached to the billing account in question.
Steps to reproduce:
Look at the billing exports page. Try to select a project not attached to that billing account
Other information (workarounds you have tried, documentation consulted, etc):