This message was deleted.

So I think despite the phrasing of that error the snapshot will still have written out, and you can probably get it to read back in by setting

--disable-integrity-checking

when running the next

pulumi up

. But please raise an issue about this, it's very likely an engine bug that the snapshot got into this state in the first place.

@echoing-dinner-19531 sadly no dice, i get the same error with that flag passed

Copy code

3.95.0

Can you try updating the CLI. I very recently fixed an issue with snapshots and replace operations so this might already be fixed.

also no dice 😞

Almost certainly due to --target. It's overdue a careful look at how it does/should work. If you can easily-ish rework to not use --target that would be my top suggestion.