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
@@ -597,8 +597,8 @@ cannot be listed or has no marker file.
|
||||
|
||||
### `snapshot remove <snapshot-id>`
|
||||
|
||||
Removes one snapshot. The argument must be a snapshot ID. A remote key is not
|
||||
accepted.
|
||||
Removes one snapshot. The argument is a snapshot ID, a remote key or the leading
|
||||
part of a remote key.
|
||||
|
||||
It needs the [lock](#locking). It needs permission to list and delete at the
|
||||
destination, unless you give `--local-only`. It needs no private key.
|
||||
@@ -618,7 +618,7 @@ Its blobs stay. Run `vaultik prune` afterwards to delete the blobs that no
|
||||
snapshot uses any more.
|
||||
|
||||
An ID that is in neither the local index nor the destination is an error. With
|
||||
`--local-only`, the snapshot must be in the local index.
|
||||
`--local-only`, the argument must be the ID of a snapshot in the local index.
|
||||
|
||||
The deletion at the destination can fail, for example when the destination is
|
||||
unreachable or has no marker file. What happens then depends on where the
|
||||
|
||||
Reference in new issue
Block a user