We've got multiple people working on stacks in the same sandbox. As a result, sometimes resources get messed with/deleted manually while we build out process. But a

pulumi destroy

blows up when resources aren't present to delete. Is there/could there be, a

--force

flag that will ignore resources that aren't present?

Have you tried running

pulumi refresh

before

destroy

?

Yes, it fails all over the place so I end up exporting the stack, deleting ALL resources, and re-importing. Then I delete the underlying EKS cluster and start building it up from scratch.

@incalculable-engineer-92975 could you please file an issue here? The “warning: went to delete resource, but wasn’t found” seems like a reasonable thing to do for the

pulumi destroy

case. Though ideally a

pulumi refresh

followed by

pulumi destroy

should “just work”. So if you could elaborate on “it fails all over the place”, that would be good too. Since if there are problems with that approach we definitely should look into it and fix them as possible.

This has come up several times - and I thought we had an issue but wasn't able to find it either of the last two times it's been raise. I opened https://github.com/pulumi/pulumi/issues/3304 to track. That said - it would be useful to have details on your usecase about what failures you see when you

refresh

then

destroy

(though in general, I can definitely imagine this not working fully if there are fundamental things broken in your stack due to interference outside of Pulumi).