While publishing the new MSSQL provider I noticed that the a

Question

While publishing the new MSSQL provider I noticed that the associated step in the GitHub workflow has an error referencing the dotnet version in the matrix build ref to picture It seems that the error can be found in most of the providers published via < C037PV12W6L|pulumiverse> because mostly the file `release yaml` is copied around by provider maintainers < C04NPQTRKM4|package authoring> So I m wondering why the publishing step works anyway and if this is something that has to be fixed in all affected providers < limited rainbow 51650>

limited-rainbow-51650 · Answer

< big architect 71258> as an extension to the `schema tools` issue I m working on I have a related branch for reusable workflows which will make use of the patched schema tools Once this is fixed I ll be testing it in a provider I maintain myself before I will communicate to roll this out for the other providers

big-architect-71258 · Answer

< limited rainbow 51650> This is awesome But why is the problem I described with referencing the dotnet version not a real issue in the provider publishing process I would have assumed that the wrong reference would break the GitHub workflow

limited-rainbow-51650 · Answer

Can t answer this on the spot to be honest There are so many variations these days on the workflows that I would need more time to investigate this individual case

big-architect-71258 · Answer

< limited rainbow 51650> Perhaps the publishing process of the MSSQL provider will now fail because I corrected the variable reference We ll know if you approve the PR again because my last push about the invalid reference reset your initial approval Sorry BTW for this chaos I should ve noticed the issue with the invalid variable reference earlier

big-architect-71258 · Answer

< limited rainbow 51650> The publishing process once again crashed not because of something with the dotnet version variable reference but in the dreaded `Check worktree clean` step I took every precaution I know of especially using the same Go Version locally to create the SDK and the provider as within the pipeline Can you help me here to figure out why `tfgen` created a new `schema json` what changed the Python SDK what eventually stopped the pipeline The publishing process is definitely something that makes me think to stop contributing Sorry to say but it s really frustrating

big-architect-71258 · Answer

Oh and needless to say before I create a new release which triggers the publishing workflow I issue `make build sdks` locally and check with `git status` manually if the worktree stays clean

big-architect-71258 · Answer

Okay I could reproduce the issue when I use an empty GO 1 20 4 Container and manually issue all steps of the build pipeline in it But I simply can t spot the difference why my local dev environment doesn t change the worktree Cleaning the GO environment didn t work `go clean cache modcache fuzzcache`

big-architect-71258 · Answer

Okay I had missing resource plugins Locally those plugins where installed But not in the empty build environment When I clean my Pulumi environment I now can reproduce the change of the worktree locally

big-architect-71258 · Answer

< limited rainbow 51650> Would awesome if you could approve my hopefully last PR to fix the GitHub workflow for the MSSQL provider

big-architect-71258 · Answer

< limited rainbow 51650> Thanks

big-architect-71258 · Answer

< limited rainbow 51650> it s seriously a constant struggle zany face man facepalming skin tone 3

big-architect-71258 · Answer

< limited rainbow 51650> I started a checklist for provider maintainers about what things need to be taken care of to end up with a successful publishing pipeline Perhaps you can have a look and tell me if I missed something

big-architect-71258 · Answer

< limited rainbow 51650> I m a little embarrassed now but could you approve the pull request again

big-architect-71258 · Answer

WAAAHHHHOOOO grinning < limited rainbow 51650> Many thanks for approving the bunch of PRs

limited-rainbow-51650 · Answer

< big architect 71258> all credit to you for persisting to get this working tada

big-architect-71258 · Answer

< limited rainbow 51650> By documenting the most prominent traps you can fall while publishing a provider I hope the next time I ll be much quicker And of course I ll update my Cookiecutter template to reflect the last insights