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

Is `pulumi destroy` what you're looking for? This will delete all running cloud services in the stack. But the stack itself, including history and config will still exist. `pulumi stack rm` will delete all history and config for a stack.

<https://www.pulumi.com/docs/reference/cli/pulumi_destroy/>

thanks for the info <@UQ8K13T7X> - I think so, funny how obvious that was. I'm still confused though why my devs are commenting out :thinking_face:

what about using a destroy but keeping other things like VPC and subnet setups..? with just the `--target-dependents` option?

For foundational resources like VPCs that you never want to delete, it's fairly common to put them in a separate stack, and then use them in another stack via stack references.