Skip to content
SHC Docs

shc finish-forward

finish an interrupted move or rename that the daemon refused to resolve itself

The daemon refuses to revert a move that was interrupted after it had torn down a source deployment: past that point the target may hold the only running copy. This is the exit from that refusal: it finishes the operation instead.

It does not take the dead process’s word for anything. Before it tears down anything else it re-observes the target’s health, re-measures the source deployments still standing, and re-checks that the target holds their bytes. If any of those cannot be answered it refuses.

Run shc interrupted first, on this node, to get the operation id.

shc finish-forward <operation-id> [flags]
-h, --help help for finish-forward
--config stringArray extra YAML config file to layer on top of auto-discovered config; repeatable, later files win
-d, --debug enable debug mode (default: $SHC_DEBUG)
-e, --environment string environment name (default: "prod", or "default" on an estate with no licence and no trial; $SHC_ENVIRONMENT and shc ctx -e override it, and the "master" tenant is always "default")
--exclude string comma-separated dotted paths to drop
--fields string comma-separated columns/keys to show (and their order)
--filter string comma-separated dotted paths to keep (drops everything else)
-o, --output string output format: tty|text|json|yaml (default: $SHC_OUTPUT)
-s, --stack string stack name (default: $SHC_STACK)
-t, --tenant string tenant name (default: $SHC_TENANT)
-v, --verbose verbose output (default: $SHC_VERBOSE)
  • shc - Selfhosted Cloud CLI