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.

Pulumi Community

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.

<@U01JU92UY82> would you mind opening an issue in <https://github.com/pulumi/pulumi> to track your suggestion?

<https://github.com/pulumi/pulumi/issues/8458>