If pressed ctrl -c while pet is running, pet itself will be cancelled.
sadayuki-matsuno opened this issue · 2 comments
After accessing the remote terminal using the pet command, pressing Ctrl-C kills the pet itself and also kills the remote connection.
Below is the result of pressing Ctrl-C when connecting ssm with aws cli
Starting session with SessionId: matsuno-0592da39a5e3bc810
$
$
$
$ Cannot perform start session: read /dev/stdin: input/output error
Ah now I see what your PR was about. So you were accessing a remote terminal using a pet snippet and then you expect ctrl-c to shutdown the remote process only, not Pet, and not your connection!
Definitely an important need.
Can you foresee any problems with having ctrl-c disabled in pet globally?
I'm trying to think whether or not this should be a snippet-specific flag maybe so we don't do it globally. But not sure if running globally is a problem at all.
Need to make sure this doesn't apply to places where we're doing pet search or other pet-specific menus where Ctrl-C is a valid way to exit out of these pet commands.