Hey guys a few weeks ago I worked in the

Question

Hey guys a few weeks ago I worked in the provider I also created a PR to add it to the registry 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

big-architect-71258 · Answer

< fierce art 88136> 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

fierce-art-88136 · Answer

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

big-architect-71258 · Answer

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

fierce-art-88136 · Answer

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

big-architect-71258 · Answer

< fierce art 88136> have you created the v0 0 6 release BEFORE or AFTER the PR to the registry has been merged

fierce-art-88136 · Answer

before

fierce-art-88136 · Answer

shall I create another release maybe

big-architect-71258 · Answer

Yes simply create a v0 0 7 The registry should pick up the new release on the next run

big-architect-71258 · Answer

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

fierce-art-88136 · Answer

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

big-architect-71258 · Answer

You re welcome

fierce-art-88136 · Answer

< big architect 71258> can you approve this PR

fierce-art-88136 · Answer

so next I will push the new tag

fierce-art-88136 · Answer

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

big-architect-71258 · Answer

I think the workflow will run tomorrow morning again

fierce-art-88136 · Answer

< limited rainbow 51650> can you take a look here I see there was added a PR for another provider but there is none for ESXi

limited-rainbow-51650 · Answer

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>

fierce-art-88136 · Answer

Let me know if I can help somehow

limited-rainbow-51650 · Answer

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>

limited-rainbow-51650 · Answer

< fierce art 88136>

limited-rainbow-51650 · Answer

< fierce art 88136> 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

fierce-art-88136 · Answer

Thank you < limited rainbow 51650> will check it out later on and see if the PR will be created slightly smiling face

limited-rainbow-51650 · Answer

I ll keep an eye on it also

limited-rainbow-51650 · Answer

Hurrah <https github com pulumi registry pull 3214>

limited-rainbow-51650 · Answer