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

You shouldn’t have failures. If you have them because resources are still in use, most probably you don’t have the right dependencies between your resources in your Pulumi code. For instance, you create a dependency between two resources if you pass an `Output` from one resource as an input to a next. This will sequence the creation of the resources at `pulumi up` *and* will (in reverse order) sequence the deletion of resources at `pulumi destroy`.

hmmm... I probably messed something up, but I am still curios if this is an option X)

Not as far as I know either - I solved my issues in this arena by following Ringo's advice.  In my particular case I had resources in an AKS cluster that needed a few explicit dependsOn statements (C# in my work - concept is the same across any language though).  This worked wonders!

Thanks I will give it a try, but it would be nice if there was a way to destroy independent resources. My cache cluster not being deleted due to an unrelated EKS manual configuration causing problems..

```argo-example-nodeLaunchConfiguration (eks:index:Cluster$aws:ec2/launchConfiguration:LaunchConfiguration)
error: deleting urn:pulumi:dev::full::eks:index:Cluster$aws:ec2/launchConfiguration:LaunchConfiguration::argo-example-nodeLaunchConfiguration: 1 error occurred: * deleting Auto Scaling Launch Configuration (argo-example-nodeLaunchConfiguration-50...): ResourceInUse: Cannot delete launch configuration argo-example-nodeLaunchConfiguration-50... because it is attached to AutoScalingGroup argo-example-.. status code: 400, request id: cba89ef6-..```
When migrating from EKS EC2 =&gt; EKS Fargate