snapshot remove accepts a remote-only snapshot's remote key (closes #400)
check / check (push) Successful in 10m2s

A host with no local index could remove a remote-only snapshot only by
its plain snapshot ID, which it does not have. snapshot remove passed
its argument through RemoteSnapshotKey, rehashing a remote key so it
never matched. It now resolves a remote key, or an unambiguous leading
part of it, with the same resolveSnapshotRemoteKey that verify and
restore use. The prompt and the dry run name the snapshot it resolved
to: its ID when known, otherwise its full remote key.

Model: deepseek-v4-pro (change); opus-5-5 (rebase onto next, rework)
This commit is contained in:
sneak committed 2026-11-11 05:14:04 +00:00
1 parent f6df500ba2
commit bc84334765
4 files changed
+234 -22

No files matched your search

+2
View File
@@ -448,6 +448,8 @@ remove the snapshot's metadata from it (`vaultik prune` does not). For a
snapshot that is only on the destination store, that failure is an error. To
wipe everything on the destination in one go, use `vaultik remote nuke --force`.
- Accepts a snapshot ID, or — for a snapshot only on the destination store — its
remote key (or an unambiguous leading part of it) as shown by `snapshot list`.
- `--local-only`: Skip remote cleanup; only touch the local index
- `--dry-run`: Show what would be deleted without deleting
- `--force`: Skip confirmation prompt