Rebased onto next, where `snapshot remove` takes a snapshot ID, a remote key or the leading part of a remote key (#400). The README and `snapshot remove --help` still said a remote key is not accepted. With `--local-only` the argument must still be the ID of a snapshot in the local index: that mode does not look the key up at the destination. Model: opus-5-5
This commit is contained in:
1 parent
b2c8d75bcc
commit
db06c5eab4
2 files changed
+9
-9
No files matched your search
@@ -379,14 +379,14 @@ 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.
|
||||
|
||||
The argument must be a snapshot ID: a remote key is not accepted. An ID
|
||||
that names no snapshot in the local index or on the destination store is
|
||||
an error. Needs permission to list and delete objects on the destination
|
||||
store, unless --local-only is given.
|
||||
The argument is a snapshot ID, a remote key or the leading part of a
|
||||
remote key. An ID that names no snapshot in the local index or on the
|
||||
destination store is an error. Needs permission to list and delete
|
||||
objects on the destination store, unless --local-only is given.
|
||||
|
||||
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
|
||||
must then be in the local index.
|
||||
snapshot locally without touching the destination store); the argument
|
||||
must then be the ID of a snapshot in the local index.
|
||||
|
||||
If removing the snapshot's metadata from the destination store fails (for
|
||||
example because the remote is unreachable), the local-database removal
|
||||
|
||||
Reference in new issue
Block a user