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

this has happened to me before - pulumi will bake the version of the provider you are using into the state file. so even if something was broken and you are now using a new version of the provider, during the diff it will still install the old version alongside the new version of the provider. normally that is OK but if the old version has a bug and cannot even run, you are in a tight spot

i got around it by a hacky workaround: <https://github.com/pulumi/pulumi-aws/issues/1501#issuecomment-844280327>
basically install the new version, and then `cp` it to the location of the old version, so when pulumi tries to run the old version it is actually running the new version

you'll get some warnings, and it is not a supported scenario, but it did get me out of one bind