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

image.png

Hi
I’m upgrating our pulumi provider (to sync to the latest version of our TF provider)
and as usual, I have an error

This time is during the release github action.

Unfortunately all of my latest upgrade providers had a problem.

Is it possible to have a website, a link, which can be a “source of truth” and a changelog to know all the changes we must realize? :slightly_smiling_face:

the fact is when we run the upgrade-provider script, it updates several tools like the bridge and the SDK too. So with a changelog, it can help to find and fix the issues :slightly_smiling_face:

I fixed the issue by upgrading cosign-installer step and create a new git tag and a new release again but I really think that a simple “upgrade”/sync” should not have to be painful :pray:

Hi, Aurelie, sorry you had issues with this. We are trying to make this process as easy as possible, so we'd really appreciate if you'd report any bugs you face in the repo <https://github.com/pulumi/upgrade-provider>

Your issue here does not look like something I've seen before.

Can you please post some more details here? What is the `cosign-installer` step doing? I don't believe we use this action internally for providers. How did you end up fixing the issue?