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

Was that an update of the puiumi cli or the SDK versions?

Both cli and pulumi-python, I've tried to rollback everything but pulumi still tries to rename most of my resources, same thing happening on multiple stacks too

You might want to open an issue for this. If you can include the rest of the update diff we might be able to see what's triggering the change.

Sure, you mean a support ticket or a GitHub issue ?

If you have enterprise support do it via that, else just a github issue.

I believe it was a bug introduced in Pulumi 3.66.0 and fixed in Pulumi 3.68.0

I'm still wrapping my head around it, but it seems to have been triggered by a combination of using `--target` and, in my case, Pulumi 3.67.1

The way I managed to recover was to rollback to a previous version of the Pulumi stack and then run a bunch pulumi refreshes and pulumi imports to match my latest changes, since I had built new infrastructure

Pulumi was trying to replace my whole infrastructure before that

Thanks a lot for the feedback <@U013QM2EK7Y> , did you just download a precious version of the stack and run a `pulumi stack import` ? I was planning to do that if I didn’t find any other fix

I basically went back in time, one by one, until I reached one that wasn't broken. To be fair, I only expect you to need to go back one or two versions.

Found this issue, definitely the same problem that we encountered: <https://github.com/pulumi/pulumi/issues/12964|https://github.com/pulumi/pulumi/issues/12964>

<@U02J3T6A8LB>: do you know if there is a recommended way to fix the problem from the GitHub issue ?

If you've got a backup of the old state just importing it would probably be easiest. If __defaults got deleted I'm not sure a refresh alone will fix that.

I'm sure that simply using `refresh` doesn't work, because I've been dealing with this since Thursday...

Yes using refresh 100% doesn't work, will try an import of an old state tomorrow morning :crossed_fingers:

I had to go back a long while (1 month+) for some of our stacks, but everything is back working :tada:

Thanks again <@U013QM2EK7Y>, I owe you a beer (or a bunch of)

Glad you were able to solve it so quickly!