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

I everybody! I have a simple question: I run a pulumi up with tho big charts: the cli is running for more than half an hour now and I would like to do something like a pulumi destroy. I tried logging in with another client and it says I should delete the lock. Is there an easier/faster way to proceed in such cases?

you can remove the lock with `pulumi cancel`

I posted a question here as well <https://stackoverflow.com/questions/71968562/how-to-stop-gracefully-a-pulumi-up-command>

Is it safe to run pulumi cancel and then pulumi destroy?

<@U03CJHZEPMH> yes that should be safe, I replied on your stackoverflow questions as well in more depth

I did not quite get what is the overall sequence of commands you would suggest. I already tried a ctr+c once and it left all the resources spread in the cluster which I would like to avoid. What is your suggestion?

ctrl+c will simply stop the operation. you'll need to run `pulumi destroy` after that

are you saying you'd like to interrupt the running process and have it automatically clean up after you?

that isn't possible, and I'm not aware of any tool that can do that. You could possibly achieve it by creating your own solution with Automation API

Ok, and what is that goes nearest to that? ctrl+c and pulumi destroy? or pulumi cancel?

ctrl+c and pulumi destroy is pretty much the same as pulumi cancel and pulumi destroy

my pleasure! let us know any of other ways we can help

btw the pulumi cancel does not destroy the lock

If you think I could get my question better on stack overflow, I would be happy to help other people too

are you running it from the same directory as your program?

```error: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or manually delete the lock file(s).```

oh, you're using the the open source backend. in that case you'll need to manually remove it from your S3 bucket, it's managed by the bucket itself