Let snapshot remove accept a remote-only snapshot's remote key (closes #400)
check / check (push) Failing after 18m27s
check / check (push) Failing after 18m27s
snapshot remove hashed its argument into a remote key, so the remote key that snapshot list shows for a remote-only snapshot never matched. A remote key or a leading part of it is now resolved with resolveSnapshotRemoteKey, as snapshot verify and snapshot restore do. Model: opus-5-5
This commit is contained in:
1 parent
1df6867cd4
commit
fb33bcf6b1
4 files changed
+67
-13
No files matched your search
@@ -468,10 +468,12 @@ destination store. Blobs are NOT touched — deleting blobs requires reading eve
|
||||
remaining remote manifest (the destination store may hold snapshots this host
|
||||
doesn't know about), which is what `vaultik prune` does. The command prints the
|
||||
`vaultik prune` invocation to run as a follow-up only when it removed the
|
||||
snapshot's metadata from the destination store, and never under `--json`. An ID
|
||||
that names no snapshot in the local index or on the destination store is an
|
||||
error; with `--local-only`, the snapshot must be in the local index. Local row
|
||||
cleanup (files, chunks, blobs the snapshot was the last referrer for) runs
|
||||
snapshot's metadata from the destination store, and never under `--json`. It
|
||||
accepts the same identifiers as `snapshot restore`: a snapshot ID, or a
|
||||
remote-only snapshot's remote key (or an unambiguous leading part of it). An
|
||||
identifier that names no snapshot in the local index or on the destination store
|
||||
is an error; with `--local-only`, the snapshot must be in the local index. Local
|
||||
row cleanup (files, chunks, blobs the snapshot was the last referrer for) runs
|
||||
automatically. If removing the snapshot's metadata from the destination store
|
||||
fails (for example because the store is unreachable, or the local index holds
|
||||
snapshots and the destination answers that it has no `vaultik-destination.txt`),
|
||||
|
||||
Reference in new issue
Block a user