From 6cc2bec5ddcd9bd2cec7dd825f4d3cb58b52d8b2 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Tue, 23 Jan 2024 19:09:04 +0100 Subject: [PATCH] apply suggestion from review --- changelog/unreleased/issue-4251 | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/changelog/unreleased/issue-4251 b/changelog/unreleased/issue-4251 index 5aeb50062..d1d3f4508 100644 --- a/changelog/unreleased/issue-4251 +++ b/changelog/unreleased/issue-4251 @@ -1,15 +1,16 @@ -Enhancement: Support reading backup from a program's standard output - -When reading data from stdin, the `backup` command could not verify whether the -corresponding command completed successfully. +Enhancement: Support reading backup from a commands's standard output The `backup` command now supports the `--stdin-from-command` option. When using -this option, the arguments to `backup` are interpreted as a command. `backup` -then executes the command and stores its standard output in the backup. This -enables restic to verify that the command completes with exit code zero. A -non-zero exit code causes the backup to fail. +this option, the arguments to `backup` are interpreted as a command instead of +paths to back up. `backup` then executes the given command and stores the +standard output from it in the backup, similar to the what the `--stdin` option +does. This also enables restic to verify that the command completes with exit +code zero. A non-zero exit code causes the backup to fail. -Example: `restic backup --stdin-from-command mysqldump [...]` +Note that the `--stdin` option does not have to be specified at the same time, +and that the `--stdin-filename` option also applies to `--stdin-from-command`. + +Example: `restic backup --stdin-from-command --stdin-filename dump.sql mysqldump [...]` https://github.com/restic/restic/issues/4251 https://github.com/restic/restic/pull/4410