shc recover
recover deployments from backup archives
Flags as shc recover registers them (ce modules/app/commands/stack_lifecycle.go). The generated page with the full help text is shc_recover.
This is a single-action command (no subcommands). It takes no node: to hold a recovered deployment to a place, change its --where afterwards (Relocating a deployment).
| Flag | Type | Required | Help |
|---|---|---|---|
-b / --from-backup | list[str] | no | backup file to recover from (<backup>[=<target>]; repeatable) |
-f / --file | str | no | single backup file to recover from (.bak or .bkg) |
--consistency-id | str | no | recover a consistency group directly from the restic store, no .bkg export; takes precedence over --file and --from-backup |
-e / --environment | str | no | target environment |
--skip-integration | list[str] | no | skip integration during recovery |
--rename | list[str] | no | rename stacks during recovery (<old>=<new>) |
--override | list[str] | no | override ingress hostnames ([<stack>:]host:<old>=<new> or [<stack>:]hosts=<new>) |
--runtime | str | no | target runtime (docker, podman, incus or apple) |
--storage | str | no | storage backend for every recovered stack, overriding the one recorded in each backup |
--secrets-password | list[str] | no | candidate password to decrypt backup secrets (repeatable; tried after the vault master) |
--secrets-password-file | list[str] | no | file of newline-separated candidate passwords (repeatable) |
--dry-run | bool | no | show what would be recovered without executing |
-y / --yes | bool | no | skip the confirmation prompt |
shc@docs:~$