rsconnect kill <content_id> [<job_id>]

[nealrichardson]

There is a Connect API for this but no convenience utility to reach it.

I'm assuming that in the average use case, there's not a specific process associated with a Content that I want to kill, I just know that my app is hung or consuming too much memory and I want to kill "it" (however many processes it has) and restart it. So if <job_id> isn't provided, it kills all processes associated with <content_id>.