Hi everyone. Has anyone idea on how to enable billing using the native gcp provider

You can set or update the billing account associated with a project using the [

projects.updateBillingInfo

] (/billing/reference/rest/v1/projects/updateBillingInfo) method.

Is the pulumi docs suggesting that we are supposed to use the relevant gcp api to update the billing https://cloud.google.com/billing/docs/reference/rest/v1/projects/updateBillingInfo ? Thank you

I believe the legacy provider is still required for enabling APIs atm, but I'll check and see if that's changed

Thank you @quiet-wolf-18467. Sorry I am still confused 😞 Unless I am mistaken this is not related to enabling an api service. My intention is using the native provider to: • create a new account ✅ • link the new account to billing account (what otherwise I would be able to do in the gcp console as exemplified in the attached screenshot) I know this is achievable in gcp _Classic _pulumi provider by specifying `billing_account` I was under the impression that pulumi is migrating the providers from Classic (which likely is going to be deprecated at some point) to the native one. If that's the case it is a bit worrying (unless I misunderstand something) that such basic functionality is lacking. Plus I have no idea what

projects.updateBillingInfo

is or how to make use of it. I confess I did not read all the docs throughout - but I was not able to find find for sure what

projects.updateBillingInfo

is: 1. is it a pulumi method? 2. is it a reference to the gcp api and I am suppused to submit an api (like in http api call) to enable billing https://cloud.google.com/billing/docs/reference/rest/v1/projects/updateBillingInfo

You can set or update the billing account associated with a project using the [

projects.updateBillingInfo

] (/billing/reference/rest/v1/projects/updateBillingInfo) method.

Sorry @acoustic-plumber-33876, I think I misunderstood your question initially. I’m re-reading

Ohh thank you, that answers my question 🙂 So 2 quick follow up questions: 1. is the plan to port all functionality to the native providers? 2. are the 'classic' one eventually going to be deprecated?

1. Yes, definitely. Anything documented in Google’s discovery APIs should be handled by the new native SDKs, i’m not sure why this isn’t; but I’ll try to find out

Thanks a lot. I guess that is it for now. However if it happens to find more regarding #1, please let me know 🙂