I can explain the problem a bit more, but I don’t think we settled on a desired behavior (it was before we had the handy issue template).

Context

coder server --dev is great for kicking the tires and everything is in-memory, which is a double edged sword. I could provision a bunch of infrastructure, and then shut down Coder with control c and that infrastructure will spin down.

The problem

However, I usually hit cntrl+c twice on terminal applications when I see it’s hanging a bit. Kind of like spamming alt f4 to close things. I am assuming others do this too. The issue is, when I do this, the “terraform delete” stops. Servers may stay up forever, and Coder will forget about them next time it runs so I’m paying a lot of $$$

Here’s one suggestion

Current behavior:

start coder with coder server --dev
create workspaces
hit cntrl c
hit cntrl c again quickly to speed up shutting down. however, all your test infrastructure will remain online :(

Desired behavior (suggestion):

start coder with coder server --dev
create workspaces
hit cntrl c
EDIT: hit cntrl c again
see dialog “Coder is shutting down your test workspaces so they don’t incur cloud costs. If you close Coder now, these servers will remain up. Are you sure? (y/n)”
Realize you want to shut down the workspaces, hit n and wait

Add double confirmation for SIGINT on coder --dev #631

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Add double confirmation for SIGINT on `coder --dev` #631