Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Very good repro of the behaviour here: #3289

Essentially, the setup is that you have an apigateway restApi resource with a Resource and Deployment, with the Deployment triggering on some property of the resource.

If the Resource resource is deleted, then pulumi would recreate the Deployment resource before deleting the Resource resource. This causes the old Resource to still be deployed since Deployment captures the snapshot of the state.

Seems like quite a few people have hit it but there's not much we can do about it from the provider side. We should at least document it better.

There's also some details on workarounds here: #3289 (comment)

Affected area/feature