Let snapshot remove accept a remote-only snapshot's remote key (closes #400)
check / check (push) Successful in 13m35s
check / check (push) Successful in 13m35s
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 was merged in pull request #458.
This commit is contained in:
1 parent
1df6867cd4
commit
d747ddef3a
4 files changed
+114
-13
No files matched your search
@@ -331,8 +331,10 @@ 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.
|
||||
The snapshot may be named by its ID or by its remote key, which
|
||||
'snapshot list' prints for a remote-only snapshot. An unambiguous
|
||||
leading part of the key is enough. An identifier that names no snapshot
|
||||
in the local index or on the destination store is an error.
|
||||
|
||||
Use --local-only to skip the remote half (e.g. when you want to forget a
|
||||
snapshot locally without touching the destination store); the snapshot
|
||||
|
||||
Reference in new issue
Block a user