Skip to content
SHC Docs

shc operation cancel

stop an install, update, start or restart in flight

Stops the install, update, start or restart running as operation . The operation ends failed (X499052OPRCNL, naming who cancelled it) through its own failure path: an install rolls back, and the deployment’s operation claim is let go, so the next install, update or uninstall of it is taken. It follows the operation to its end unless --no-wait. A cancelled start or restart leaves its deployment as a failed one does: its replicas stay desired running and its status is not set to running. The next start brings it up.

An operation that already ended is left as it is, and the command says how it ended. An uninstall is not cancelled: it runs its teardown to its end (X409054OPRNCN). An id is answered as shc operation follow answers it: another tenant’s operation is refused (X403904NOTENT), and one on a deployment hidden from the caller, or an unknown id, is not found (X404050OPRNOF). It takes stack:manage on the operation’s tenant.

shc operation cancel <id> [flags]
-h, --help help for cancel
--no-wait return once the operation is told to stop, without following it to its end
--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)