Change Details

If while a deployer is running scap, their local connection goes down, there is chance of `helm` being left in a limbo state. Deployers should always run scap within a server side tmux/screen we should [] update relevant documentation to stress how important it is to run within a tmux/screen session [] add a warning in scap itself, so a deployer will be reminded/encouraged to use tmux/screen [] possibly add a switch to override this warning

If while a deployer is running scap, their local connection goes down, there is chance of `helm` being left in a limbo state - see T361720. Deployers should always run scap within a server side tmux/screen we should [] update relevant documentation to stress how important it is to run within a tmux/screen session [] add a warning in scap itself, so a deployer will be reminded/encouraged to use tmux/screen [] possibly add a switch to override this warning

If while a deployer is running scap, their local connection goes down, there is chance of `helm` being left in a limbo state - see T361720. Deployers should always run scap within a server side tmux/screen we should [] update relevant documentation to stress how important it is to run within a tmux/screen session [] add a warning in scap itself, so a deployer will be reminded/encouraged to use tmux/screen [] possibly add a switch to override this warning