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

`delete: "kubectl delete --all namespaces",` seems to capture the intention

But how does it know *only* to run that command when the right cluster is deleted?

Actually i think i found the answer in another example:
&gt; Note that implicit and explicit (`dependsOn`) dependencies can be used to control the order that these `Command` and `CopyFile` resources are constructed relative to each other and to the cloud resources they depend on. This ensures that the `create` operations run after all dependencies are created, and the `delete` operations run before all dependencies are deleted.
so the Command is *only* run if *all* implicit or explicit dependencies fulfill the create/delete/etc event. So if a Command has two dependencies, but only 1 is being deleted, it will not run

That's good to know alright, but in that example, there's only one dependency.

When the cluster is deleted, the command has to be deleted first (dependency in `environment`).

Yeah. Not knowing what would happen if there are multiple dependencies, for some reason, totally derailed me train of thought. Thanks for helping out :slightly_smiling_face: