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

Did you follow the suggestions in the last paragraph?

<@UB3BGTV63> yes , followed it. But I deleted the pending operation item and imported the stack. But I am still stuck. It is an endless loop of importing and then
```
aws:ec2:LaunchConfiguration (monitoring-nodeLaunchConfiguration):
    error: pre-step event returned an error: failed to verify snapshot: resource urn:pulumi:naveen::aws-arcus-kitchensink::arcus:cluster$eks:index:Cluster$kubernetes:core/v1:ConfigMap::local-dev-naveen-nodeAccess refers to unknown provider urn:pulumi:naveen::aws-arcus-kitchensink::arcus:cluster$eks:index:Cluster$pulumi:providers:kubernetes::local-dev-naveen-eks-k8s::0f92a33a-3eea-4721-b1e7-423c3686666b

  pulumi:pulumi:Stack (aws-arcus-kitchensink-naveen):
    error: update failed
```

I don’t want to leave dangling resources.

If there are resources still being managed by the stack, and you want to automatically destroy them, you will need to run a `pulumi destroy` yourself, presumably after doing a `pulumi cancel`.  If you can't successfully delete any resources (I'd love to understand what these are), then you can maually delete in your coud provider and run <https://www.pulumi.com/docs/reference/cli/pulumi_state_delete/> to remove from your Pulumi stack so you can continue to destroy other resources.

You can also force delete the stack yourself with `pulumi stack rm -f` - though that will then orphan all resources (and you will then want to clean them out manually in your cloud provider).