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

<https://github.com/pulumi/pulumi-aws/issues/1458>

It's going to take some time for the fix for this, but the workaround I describe at <https://github.com/pulumi/pulumi-aws/issues/1458#issuecomment-825333911> is a way to move past this and should be a sufficient way to move past this for each stack you need to.

Ekk. Between dev stacks + hosted env stacks, that’ll be like 25 stacks we have to do surgery on.

We can help you with a script to do this if you'd like?

We can just pin to v2.x until it’s fixed in v3.x