Webhook For Teardown

[logston]

Please describe what you would like to see in ContainerSSH

Currently ContainerSSH provides a webhook for authentication and configuration of a container (or pod) that are triggered by an SSH connection to the ContainerSSH server. Upon successful authentication, the container described by the configuration is instantiated. Upon SSH disconnect, the container is removed by the server.

We would like a third webhook which would receive the status of the removal.

Please describe your use case

In order to run a ConatinerSSH created container successfully in a k8s environment, we choose to spin up auxiliary services (VMs, pods, etc). We would like some signal to know when we can tear down those extra resources.

[ghost]

Hey @logston this is great idea and should be fairly simple to implement. However, we currently don't have capacity to add additional features. If you or anyone else would be willing to implement this, we'd be more than happy to review the PR.