Expose billing exports through API [70525274]

Assigned

Feature Request

Status Update

No update yet.

Description

ro...@admin.cleardata.com

created issue #1

Dec 11, 2017 11:10PM

Google recently announced GA support for exporting billing data to BigQuery. I don't see a way to enable this export via the API, and according to the discussion at [1], it doesn't currently exist. We need this to automate our billing aggregation for newly created billing accounts.

Thanks,
Ross

[1] -

https://stackoverflow.com/questions/46073062/how-to-enable-export-billing-information-google-cloud-using-rest-api-for-both (especially see

https://stackoverflow.com/questions/46073062/how-to-enable-export-billing-information-google-cloud-using-rest-api-for-both#comment79113679_46073062)

Comments

di...@google.com <di...@google.com> Dec 12, 2017 05:33PM

Assigned to di...@google.com.

di...@google.com <di...@google.com> #2Dec 12, 2017 09:29PM

Thanks for submitting this feature request. Product engineering team has been made aware of this request, however, I don’t have any ETA to provide for the implementation. Nevertheless, you can keep following this thread for the future updates.

di...@google.com <di...@google.com> Jun 5, 2018 01:24PM

Reassigned to gc...@google.com.

ch...@outlook.com <ch...@outlook.com> #3Jul 9, 2019 05:18PM

Hi,

I was just wondering if there is any progress on this?

Thanks
Chung

di...@google.com <di...@google.com> #4Jul 11, 2019 01:13AM

We understand your anxiety about using this product. Unfortunately, our Engineering team is still working on this product. As of now, there isn't any update from the Engineering team.

Before making a product available for the general public, it needs to be thoroughly tested so that its various inconsistencies/instabilities would be rectified or minimized. This would be beneficial not only for the public usage of but also for the quality of the product itself.

That's being said, I have already requested the Engineering team to post any updates (if available ) regarding this. Therefore, I would recommend you to visit this thread regularly any further updates regarding this will be posted here.

ge...@sky.uk <ge...@sky.uk> #5Jul 29, 2019 02:45PM

I too am interested in this feature. This is the one part we cant automate, which is a real shame for good practice.

ch...@redhat.com <ch...@redhat.com> #6Aug 6, 2019 06:41PM

I am also interested in this feature as this is missing in parity for what Amazon Web Services and Azure provide programmatically.

ma...@gmail.com <ma...@gmail.com> #7Sep 3, 2019 02:10AM

I am interested in this feature. It's a pretty time-consuming task to do this manually.

fr...@gmail.com <fr...@gmail.com> #8Oct 25, 2019 02:50PM

2 years later and still no news. Coolio

ar...@avidsecure.io <ar...@avidsecure.io> #9Oct 31, 2019 07:11AM

Interested in this feature

rr...@gmail.com <rr...@gmail.com> #10Feb 7, 2020 07:43AM

Hi,

di...@google.com is there any update for the above concern.

do...@gmail.com <do...@gmail.com> #11May 20, 2020 07:48AM

is there any update on this request ?

hi...@gmail.com <hi...@gmail.com> #12Aug 18, 2020 04:18AM

+1 ..

bh...@ntucenterprise.sg <bh...@ntucenterprise.sg> #13Sep 24, 2020 11:29PM

+1 ...

[Deleted User] <[Deleted User]> #14Dec 10, 2020 12:38PM

al...@cloud39.co <al...@cloud39.co> #15May 29, 2021 12:31AM

+1
Is there any update on this?

Message last modified on May 29, 2021 12:31AM

cc...@singlestore.com <cc...@singlestore.com> #16Jun 4, 2021 02:53PM

ma...@kursin.pp.ua <ma...@kursin.pp.ua> #17Dec 8, 2021 07:26AM

de...@ollion.com <de...@ollion.com> #18Dec 8, 2021 07:55AM

19...@gmail.com <19...@gmail.com> #19Jan 20, 2022 11:19AM

ca...@gmail.com <ca...@gmail.com> #20Feb 24, 2022 10:26PM

mu...@gmail.com <mu...@gmail.com> #21Mar 17, 2022 06:53PM

2022 stilll not added

cl...@springbokagency.com <cl...@springbokagency.com> #22Mar 23, 2022 03:16PM

fi...@techallies.org <fi...@techallies.org> #23Mar 26, 2022 02:48AM

ra...@glean.com <ra...@glean.com> #24May 10, 2022 06:21PM

he...@gmail.com <he...@gmail.com> #25Jun 10, 2022 01:35PM

fe...@gmail.com <fe...@gmail.com> #26Jun 22, 2022 02:17PM

pr...@ubiqube.com <pr...@ubiqube.com> #27Aug 18, 2022 06:17AM

ge...@endava.com <ge...@endava.com> #28Sep 2, 2022 12:00PM

la...@google.com <la...@google.com> #29Sep 15, 2022 01:27PM

da...@gmail.com <da...@gmail.com> #30Oct 5, 2022 11:27AM

va...@oracle.com <va...@oracle.com> #31Nov 21, 2022 06:10PM

[Deleted User] <[Deleted User]> #32Dec 22, 2022 06:54PM

ar...@ziffdavis.com <ar...@ziffdavis.com> #33Jan 10, 2023 12:37PM

bh...@gmail.com <bh...@gmail.com> #34Feb 1, 2023 04:59PM

Any update on this?

na...@fxinnovation.com <na...@fxinnovation.com> #35Apr 26, 2023 01:33PM

any update on this please?

al...@cloudpilots.com <al...@cloudpilots.com> #36Oct 5, 2023 12:29PM

as...@appdat.jsc.nasa.gov <as...@appdat.jsc.nasa.gov> #37Oct 17, 2023 04:11PM

Only Google and Mozilla can have a ticket assigned for 5 years and still have nothing done.

fr...@refinedscience.com <fr...@refinedscience.com> #38Nov 17, 2023 09:02PM

re...@gmail.com <re...@gmail.com> #39May 18, 2024 10:48PM

2024 still nothing
+1

ri...@pump.co <ri...@pump.co> #40Jun 11, 2024 08:25PM

on...@google.com <on...@google.com> Jul 5, 2024 09:30AM