Recently started experiencing some unexpected behavior where, after running

pulumi refresh

, Pulumi now wants to spuriously update or replace a bunch of resources that I can assert haven’t actually changed. Some examples of diffs that look wrong to me (on various resources):

~ records: [
    ~ [0]: "10.3.0.222" => output<string>
]

~ memory                 : "512" => 512

- volumes                : []

 ~ applications               : [
    ~ [0]: "Spark" => "Hadoop"
    ~ [2]: "Hadoop" => "Presto"
    ~ [3]: "Presto" => "Spark"
]

This occurs immediately after a sequence of

pulumi up

,

pulumi refresh

,

pulumi up

, without any alteration of my scripts or deliberate modification of deployed resources.

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.

Feel free to DM to @microscopic-florist-22719 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

Thanks - I’ll take a look at this.