shc reclaim
shc reclaim
Section titled “shc reclaim”free the moved-from data a relocation kept on this node
Synopsis
Section titled “Synopsis”A move renames the source deployment aside instead of deleting it, so the bytes survive a move that should not have run. This lists those trees and, with --yes, removes them.
It only sees this node. A moved-from tree is on the machine the deployment left, so run it against that node (shc --node <n> reclaim / on the host itself). nothing to reclaim from the wrong host means nothing.
shc reclaim [flags]Options
Section titled “Options” -h, --help help for reclaim --older-than duration only consider trees quarantined longer ago than this (e.g. 168h); default considers all --operation string only the trees one move produced, by its operation id -y, --yes remove the listed trees. Without it nothing is deleted and this is a reportOptions inherited from parent commands
Section titled “Options inherited from parent commands” --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)SEE ALSO
Section titled “SEE ALSO”- shc - Selfhosted Cloud CLI
shc@docs:~$