This message was deleted.

At first glance, a cascading delete would be very risky, but a protect-if-has-children opt would be very safe. And maybe some way to get Pulumi to generate a script full of all the

pulumi state delete

commands necessary to fully clean up, so that I can manually edit it myself..

Such a flag seems analogous to the

--target-dependents

flag for

pulumi up

. That flag allows the targeted deletion of a resource and anything that depends on that resource. I think that given the similarity in behavior there’s a pretty straightforward case to make here.