This message was deleted.

sparse-intern-71089

10/07/2019, 1:15 PM

This message was deleted.

tall-librarian-49374

10/07/2019, 1:22 PM

Have you tried running

pulumi refresh

before

destroy

incalculable-engineer-92975

10/07/2019, 1:31 PM

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

10/07/2019, 1:33 PM

If I do a

pulumi destroy

, it shouldn't fail on missing resources, I want them gone, so if they're gone already, bonus.

incalculable-engineer-92975

10/07/2019, 1:34 PM

Just give me a notice at the end, 'these resources weren't there to delete', 'these resources couldn't be verified as deleted since the connecting resources were missing'

colossal-beach-47527

10/07/2019, 3:32 PM

@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.

white-balloon-205

10/07/2019, 6:25 PM

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).

Open in Slack

Previous Next

Pulumi Community

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.