Fail restore for a requested path that matches nothing (closes #309)
check / check (push) Waiting to run
check / check (push) Waiting to run
snapshot restore said nothing about a requested path that matched no entry in the snapshot (a typo, a relative path, or a path through a configured snapshot path that is a symlink, whose entries are stored under the resolved directory) and exited 0, also when nothing matched at all. Each such path is now named in a warning, and restore returns an error after restoring the paths that do match. Making a path through a symlink match is not part of this change. Judgement call: when files also fail to restore, that error is the one returned; the unmatched paths are still named. Model: opus-5-5
This commit is contained in:
@@ -30,6 +30,8 @@ This command will restore files from the specified snapshot to the
|
||||
target directory.
|
||||
If no paths are specified, all files are restored.
|
||||
If paths are specified, only matching files/directories are restored.
|
||||
A path that matches nothing in the snapshot is named in a warning, and
|
||||
the command exits non-zero after restoring the paths that match.
|
||||
|
||||
The snapshot may be named by its ID or, when restoring on a host with no
|
||||
local index, by the remote key that 'snapshot list' prints for a
|
||||
|
||||
Reference in New Issue
Block a user