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

Hey guys, a few weeks ago I worked in the <https://github.com/pulumiverse/pulumi-esxi-native/> provider. I also created a PR to add it to the registry <https://github.com/pulumi/registry/pull/3015/files> which got merged. When I look at the registry there is no match found. Do you know if there is something else needed for the provider to show up?

image.png

<@U05E3UBTT5G> you can always check about the status of a community provider in thbe registry looking at the GitHub actions performed for the provider. Right now, no changes (opn PR) have been detected. Perhaps you have to back in the actions history  and verify if the registry ever correctly detected your provider.

I see, thanks will take a look if I find anything, in this case, is there another way to trigger the workflow again?

It's a scheduled workflow running twice a day. Not sure if someone would/could trigger it manually. Getting <@UK4HNFLCB> involved is always a good idea. I can remember that I had similar issues with the MSSQL provider.

I see this is the first time the job did run <https://github.com/pulumi/registry/actions/runs/6166162150>

<@U05E3UBTT5G> have you created the v0.0.6 release BEFORE or AFTER the PR to the registry has been merged?

Yes, simply create a v0.0.7. The registry should pick up the new release on the next run.

If this is successful you should see a PR in registry like the ones for my MSSQL provider.

I see, thank you :slightly_smiling_face: I didn't know the way workflow worked. Cool will check it out and see if that works :slightly_smiling_face: :pray:

<@UKHFQ233Q> can you approve this PR <https://github.com/pulumiverse/pulumi-esxi-native/pull/33/files>

I created the new release <https://github.com/pulumiverse/pulumi-esxi-native/releases/tag/v1.0.0|v1.0.0> but I see no PR in the registry side :disappointed:

I think the workflow will run tomorrow morning again.

<@UK4HNFLCB> can you take a look here? I see there was added a PR for another provider, but there is none for ESXi

Something is wrong here. Needs more investigation.
<https://github.com/pulumi/registry/actions/runs/6270503792/job/17028537875|https://github.com/pulumi/registry/actions/runs/6270503792/job/17028537875>

Found it. This line doesn't properly match your package name. `group2` becomes `native` instead of `esxi-native`. In this case, we check if there are open PRs with the package name in the subject and it finds this (unrelated) PR: <https://github.com/pulumi/registry/pull/3076>

<@U05E3UBTT5G> <https://github.com/pulumi/registry/pull/3210>

<@U05E3UBTT5G> my fix is merged. If all is well, a PR for `exsi-native` should be created less than 2 hours from now. The next scan for new releases happens at 17:30 UTC, so 18:30 our timezone.

Thank you <@UK4HNFLCB> will check it out later on and see if the PR will be created :slightly_smiling_face:

Hurrah!! <https://github.com/pulumi/registry/pull/3214>

<https://www.pulumi.com/registry/packages/esxi-native/>