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

image.png

Another weird issue, we use the automation api in an application that runs on dev under nodemon, so it restarts when you modify a file. If an `up` is running during a restart, it leaves zombie processes running. Is there a way to cancel an `up` cleanly?

Evan answered some of this over at: <https://pulumi-community.slack.com/archives/C019YSXN04B/p1609180437202900?thread_ts=1609161459.201200&amp;cid=C019YSXN04B>

I’m in the process of implementing the import/export/cancel functionality that will unlock this.

<@UQ8K13T7X>’s answer is about the way you could cancel something running from the code, which might also help in cleaning up the pulumi processes myself. And that would allow me to write code to cancel a running process. The totality of the issue is a bit more complex and all tied to each other. Instead of spamming the slack, i put a synthesis of my current understanding into the github issue: <https://github.com/pulumi/pulumi/issues/5531>