Say that snapshot remove accepts a remote key
check / check (push) Successful in 11m4s

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:
sneak committed 2026-11-17 00:30:42 +00:00
1 parent b2c8d75bcc
commit db06c5eab4
2 files changed
+9 -9

No files matched your search

+3 -3
View File
@@ -597,8 +597,8 @@ cannot be listed or has no marker file.
### `snapshot remove <snapshot-id>` ### `snapshot remove <snapshot-id>`
Removes one snapshot. The argument must be a snapshot ID. A remote key is not Removes one snapshot. The argument is a snapshot ID, a remote key or the leading
accepted. part of a remote key.
It needs the [lock](#locking). It needs permission to list and delete at the 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. 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. snapshot uses any more.
An ID that is in neither the local index nor the destination is an error. With 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 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 unreachable or has no marker file. What happens then depends on where the
+6 -6
View File
@@ -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 '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. 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 The argument is a snapshot ID, a remote key or the leading part of a
that names no snapshot in the local index or on the destination store is remote key. An ID that names no snapshot in the local index or on the
an error. Needs permission to list and delete objects on the destination destination store is an error. Needs permission to list and delete
store, unless --local-only is given. 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 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 snapshot locally without touching the destination store); the argument
must then be in the local index. must then be the ID of a snapshot in the local index.
If removing the snapshot's metadata from the destination store fails (for If removing the snapshot's metadata from the destination store fails (for
example because the remote is unreachable), the local-database removal example because the remote is unreachable), the local-database removal