Get Compute Engine instance SKU name from Cloud Billing Catalog API [111070261]

Assigned

Feature Request

Status Update

No update yet.

Description

di...@google.com

created issue #1

Jul 2, 2018 06:18PM

This is a request to have the Cloud Billing Catalog API [1] to display the SKU (Standard machine types like n1-standard-1 etc) of Compute Engine objects and their respective number of cores when calling the API with this [2] GET request [3]. It is also a request to have a GET request that returns a JSON that shows the SKU of a particular instance name.

Currently, the API does not show the Standard machine type of Compute Engine instances and it is not possible to get the SKU of a particular instance.

The implementation of this feature would prevent customers from having to parse the current output in order to get the information they need.

[1]

https://cloud.google.com/billing/v1/how-tos/catalog-api
[2]

https://cloudbilling.googleapis.com/v1/services/SERVICE_ID/skus?key=API_KEY
[3]

https://cloud.google.com/compute/docs/machine-types#standard_machine_types

Comments

de...@google.com <de...@google.com> Jul 13, 2018 09:44PM

Assigned to gc...@google.com.

ra...@gmail.com <ra...@gmail.com> #2Dec 19, 2018 03:38PM

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

al...@gmail.com <al...@gmail.com> #3Jul 3, 2019 08:07PM

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?

fj...@doalitic.com <fj...@doalitic.com> #4Jul 12, 2019 02:23PM

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.

ke...@gmail.com <ke...@gmail.com> #5Dec 30, 2019 11:12PM

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)

ka...@cloudamize.com <ka...@cloudamize.com> #6Jan 6, 2020 08:11AM

Over 3 years to get something as basic as renaming a static IP address. Any progress here?

pr...@dasinfomedia.com <pr...@dasinfomedia.com> #7Feb 17, 2020 12:03PM

Yes, I have a customer who has this exact issue too! Any updates or workarounds would be very appreciated!

sh...@cloudreach.com <sh...@cloudreach.com> #8May 17, 2020 04:20AM

Any progress in here?

mo...@gmail.com <mo...@gmail.com> #9Aug 11, 2020 03:28AM

I would like this feature as well.

sa...@gmail.com <sa...@gmail.com> #10Aug 26, 2020 08:16PM

Hello, any progress in here? Please is very frustrating.

as...@gmail.com <as...@gmail.com> #11Aug 31, 2020 03:25PM

Hi, open request for more than 3 years for a simple change. Please proceed that.

[Deleted User] <[Deleted User]> #12Oct 20, 2020 08:12PM

+1. :(

mi...@gmail.com <mi...@gmail.com> #13Nov 27, 2020 07:37AM

We need this.

od...@deepinstinct.com <od...@deepinstinct.com> #14Apr 26, 2021 01:34PM

please add this!

mu...@gmail.com <mu...@gmail.com> #15Jul 13, 2021 01:21PM

+1 !

2m...@gmail.com <2m...@gmail.com> #16Jul 16, 2021 02:43PM

Message last modified on Jul 16, 2021 02:43PM

aw...@sap.com <aw...@sap.com> #17Oct 3, 2021 03:43PM

Comment has been deleted.

Message last modified on Oct 4, 2021 04:47AM

vi...@gmail.com <vi...@gmail.com> #18Oct 6, 2021 06:59PM

We need this please

[Deleted User] <[Deleted User]> #19Oct 21, 2021 09:35AM

[Deleted User] <[Deleted User]> #20Nov 2, 2021 07:13AM

+1

2018 =(

af...@gmail.com <af...@gmail.com> #21Dec 24, 2021 06:36AM

mu...@gmail.com <mu...@gmail.com> #22Mar 22, 2022 08:44AM

[Deleted User] <[Deleted User]> #23Mar 26, 2022 08:24AM

co...@gmail.com <co...@gmail.com> #24Jul 26, 2022 04:25AM

ka...@hcl.com <ka...@hcl.com> #25Aug 31, 2022 11:48AM

+1 (again) coming up to 5 years?

fe...@gmail.com <fe...@gmail.com> #26Oct 18, 2022 02:06AM

ra...@gmail.com <ra...@gmail.com> #27Oct 18, 2022 03:25PM

la...@gmail.com <la...@gmail.com> #28Mar 20, 2023 10:23PM

ba...@google.com <ba...@google.com> Jun 6, 2023 12:23PM

Reassigned to ba...@google.com.

ba...@google.com <ba...@google.com> Jun 23, 2023 09:44AM

Reassigned to gc...@google.com.

ra...@gmail.com <ra...@gmail.com> #29Sep 18, 2023 12:55PM

us...@gmail.com <us...@gmail.com> #30Oct 12, 2023 06:12AM

ya...@gmail.com <ya...@gmail.com> #31Oct 25, 2023 01:27PM

ti...@elastic.co <ti...@elastic.co> #32Jan 8, 2024 03:20PM

cr...@redpanda.com <cr...@redpanda.com> #33May 8, 2024 03:03PM

Please implement this