Skip to content
SHC Docs

shc rename

rename a deployment

Give a deployment a new name in its own tenant and environment. A deployment on one node stays on it. One whose replicas run on more than one node comes back with every replica on the node that runs the rename, and the plan names each replica and its node first. The command plans the rename first; --dry-run prints the plan and stops, and a run without --yes must be on a terminal. A rename does not re-render the ingress, so follow it with shc update .

shc rename <stack> <name> [flags]
shc rename paperless docs --dry-run
shc rename paperless docs --yes && shc update docs
--dry-run show what would be renamed without executing
-h, --help help for rename
-y, --yes skip confirmation prompt
--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