Skip to content
SHC Docs

shc roll-back

roll an interrupted rename back to its source name

A rename that was interrupted leaves a record, and the daemon finishes it forward at its next start. It refuses to when the rename would land on a system deployment’s name in another tenant, and the deployment then stays down. This puts it back under the name it ran under before the rename began: it undoes each step the rename reached, starts the deployment under its own name, and retires the record.

If it stops part-way the record is kept, and the next daemon start or this command again carries it on from where it stopped. Dropping a record without restoring the deployment is refused: the record is the only map of what the rename moved.

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

shc roll-back <operation-id> [flags]
shc interrupted
shc roll-back rename-corp-default-wiki
--drop retire the record without restoring the deployment (refused: the record is the only map of what the rename moved)
-h, --help help for roll-back
--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