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

We are experiencing the same error at a customer project as well! We're unable t destroy with Pulumi 2.6.0.

I'm getting the same error, but with the command `pulumi up`

I found a workaround for failing `pulumi up` : it works when adding `--non-interactive --yes` -&gt; `pulumi up --non-interactive --yes`

Hi all,

We identified the issue for this and are actively reverting the code that caused it

We will cut Pulumi v2.6.1 ASAP to fix this