No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

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

linking_billing.jpg

Thank you <@UCU9C7W73>.  Sorry I am still confused :disappointed:
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 :white_check_mark: 
• 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 <https://www.pulumi.com/registry/packages/gcp/api-docs/organizations/project/#create|gcp >_<https://www.pulumi.com/registry/packages/gcp/api-docs/organizations/project/#create|Classic >_<https://www.pulumi.com/registry/packages/gcp/api-docs/organizations/project/#create|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>
&gt; You can set or update the billing account associated with a project using the [`projects.updateBillingInfo`] (/billing/reference/rest/v1/projects/updateBillingInfo) method.

I was under the impression that com *completeness* is what one of the native goals, which again - unless I misunderstand something which is quite possible - is worrying :disappointed:
&gt;  Pulumi native providers are a new type of <https://www.pulumi.com/blog/pulumiup-pulumi-packages-multi-language-components/|Pulumi Package> that give you the most _*complete*_ and consistent interface for the modern cloud. Pulumi native providers bring the full power of the top cloud providers to the Pulumi Cloud Engineering Platform, faster and with more _*complete*_ coverage than any other infrastructure as code offering. (<https://www.pulumi.com/blog/pulumiup-native-providers/>)

Sorry <@U032A4BC48M>, I think I misunderstood your question initially. I’m re-reading

Ah, I’m really sorry but this isn’t supported yet and is currently being tracked: <https://github.com/pulumi/pulumi-google-native/issues/108>

Ohh thank you, that answers my question :slightly_smiling_face:
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

2. I don’t believe any decision has been made on that yet

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