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

<@U037R04428M> no, it should point to your github org/repo

if you look at the providers in <http://github.com/pulumiverse|github.com/pulumiverse> they are good examples

Screen Shot 2022-08-25 at 3.40.35 PM.png

Screen Shot 2022-08-25 at 3.41.58 PM.png

Hi <@UCWG26BH7> Thank you. Here is an example of what I am referring to. The imports are pointing to the pulumi directory instead. Is this done automatically once the provider is placed in the registry?

sorry I’m not really following I’m afraid, what do you mean?

These are screenshots from i.e the Cloudflare provider, which lives under the pulumi registry repo. Looking at the main.go screenshot, they are importing their pulumi provider from the pulumi repo instead i.e cloudflare “<http://github.com/pulumi-cloudflare/provider/v4|github.com/pulumi-cloudflare/provider/v4>”

In other words, why is cloudflare pointing to the pulumi registry instead of their repo org?

the provider module path is this: <https://github.com/pulumi/pulumi-cloudflare/blob/master/provider/go.mod#L1>

So the import references that

the provider go.mod is different from the SDK go.mod which is used in the registry

Got it, so once I submit the pull request under the registry that will have to be changed essentially. Am understanding it correct?

you should set the go.mod to whatever you repo path is, for example:

<https://github.com/pulumiverse/pulumi-scaleway/blob/master/provider/go.mod#L1>

Here is my go.mod for my provider

<https://github.com/pulumiverse/pulumi-scaleway/blob/master/sdk/go.mod#L1>

Notice, it’s the same as where my repo lives.

I define the module base path for codegen here: <https://github.com/pulumiverse/pulumi-scaleway/blob/master/provider/resources.go#L261>

the registry doesn’t care at all about the paths

Got it.  It just seems weird to me that all providers in the registry are pointing to the pulumi repo instead of their own repo, so it made me think that it had to be changed in order to submit to the registry via PR.

you keep saying “own repo” which I’m not understanding

there is only one repo per provider, so struggling to get my head around that

Let me change the question because I am also confused maybe. Are all the providers under the pulumi registry i.e cloudflare, f5, auth0, docker etc, created by Pulumi themselves or by the respective vendors?

they are managed and maintained by Pulumi.

there are a few in <http://github.com/pulumiverse|github.com/pulumiverse> that are managed by trhe community, including myself

Ok… that explain now… I thought that all those providers were created and maintained by the vendors themselves, which is not the case; hence the reason I thought that once I finished developing the provider, I had to change the paths to be the pulumi registry instead. That is explained now. It makes sense.

Thank you for your help understanding that. Much appreciated :slightly_smiling_face:

let me know if you need help with bridging your providers

Absolutely. Thank you again :slightly_smiling_face: