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

btw are there any good documentation on getting started with pulumi providers in Golang?

&gt; getting started with pulumi providers in Golang?
as in, writing your own provider in Golang?

Have a look at our Go provider framework: <https://github.com/pulumi/pulumi-go-provider>
To get you started, we have the following boilerplate using this framework: <https://github.com/pulumi/pulumi-provider-boilerplate>

Any further questions on getting this going can be best dropped in channel <#C04NPQTRKM4|package-authoring>

Oh, and our starter page offcourse: <https://www.pulumi.com/docs/using-pulumi/pulumi-packages/how-to-author/>

image.png

<@UK4HNFLCB> I was under the impression that you could not author your own provider in Golang due to <https://www.pulumi.com/docs/concepts/resources/dynamic-providers/|this link> but that seems to not be true, given your documentation. What is the difference between a Dynamic Resource provider and a Pulumi package?

<@U0736B5BZED> a pulumi package using the Go provider framework allows you to build your set of resource and/or component implementations (yes, they can be combined in a single package), and be consumed from *any* of the supported Pulumi languages by generated the respective SDKs for it.
A dynamic provider on the other hand can only be implemented in JS/TS and Python and is single language. We offer this in case you want to bridge a small gap in the offered Pulumi packages in our Registry.
One doesn’t exclude the other.

I am more looking for examples where I can start using existing packages like cloudflare

The idea is to
• get connected to a CF account and zones within it and then work with them to manage the state of those 