Skip to content
SHC Docs

shc interrupted

list moves and renames this node was interrupted in the middle of

A move or rename that was killed mid-flight, or whose hand-back failed, leaves a durable record. The daemon resolves most of them by itself: at its start it reverts an interrupted move and finishes an interrupted rename, and while it runs it retries a move’s revert every two minutes. The ones it refuses to resolve by itself are listed here with the command that resolves them.

It only sees this node. A record belongs to the node its operation ran on, so run it against that machine. An empty list from the wrong host means nothing.

shc interrupted [flags]
-h, --help help for interrupted
--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