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

These are the outputs of a `preview` right?

All of these look like they may cause no actual changes when you do an update. But understandably that’s not something you want to rely on (and is misleading). 

If it’s possible to create a minimal repro (or even just the full details of the diff you see) and open an issue in the main Pulumi repro we’ll have someone take a look. 

this is on a `pulumi up`. It definitely does actually destroy and re-create resources if I go through with it.

Is there a way to send you the full diff privately? Or send you a link to the view on your app console? I’d rather not post it publicly since it has a lot of our architecture in it.

Feel free to DM to <@U84HBHXS8> and myself. We’ll look into it. 

I have created a repo containing a reproduction case, and created an issue for this on the Pulumi github: <https://github.com/pulumi/pulumi/issues/2781>