summaryrefslogtreecommitdiff
path: root/obnam.md
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2020-12-23 09:44:31 +0200
committerLars Wirzenius <liw@liw.fi>2020-12-23 10:17:17 +0200
commit15ce048ca21ad517e27ab598d861ae07f817067d (patch)
tree01857ffa023c770164a9cc07d1024ed388150864 /obnam.md
parentd6584921d8bb77fd4de8b6997848599cb9d73e01 (diff)
downloadobnam2-15ce048ca21ad517e27ab598d861ae07f817067d.tar.gz
feat! add a global --config option
This breaks all invocations of the Obnam client, as the option needs to come before the subcommand name. The benefit of this breakage is simpler, less repetitive code.
Diffstat (limited to 'obnam.md')
-rw-r--r--obnam.md18
1 files changed, 9 insertions, 9 deletions
diff --git a/obnam.md b/obnam.md
index 057996d..fbbf994 100644
--- a/obnam.md
+++ b/obnam.md
@@ -795,11 +795,11 @@ and a running chunk server
and a client config based on smoke.yaml
and a file live/data.dat containing some random data
and a manifest of the directory live in live.yaml
-when I run obnam backup smoke.yaml
+when I run obnam --config smoke.yaml backup
then backup generation is GEN
-when I run obnam list smoke.yaml
+when I run obnam --config smoke.yaml list
then generation list contains <GEN>
-when I invoke obnam restore smoke.yaml <GEN> rest
+when I invoke obnam --config smoke.yaml restore <GEN> rest
given a manifest of the directory live restored in rest in rest.yaml
then files live.yaml and rest.yaml match
~~~
@@ -832,9 +832,9 @@ and a running chunk server
and a client config based on metadata.yaml
and a file live/data.dat containing some random data
and a manifest of the directory live in live.yaml
-when I run obnam backup metadata.yaml
+when I run obnam --config metadata.yaml backup
then backup generation is GEN
-when I invoke obnam restore metadata.yaml <GEN> rest
+when I invoke obnam --config metadata.yaml restore <GEN> rest
given a manifest of the directory live restored in rest in rest.yaml
then files live.yaml and rest.yaml match
~~~
@@ -851,9 +851,9 @@ and a client config based on metadata.yaml
and a file live/data.dat containing some random data
and file live/data.dat has mode 464
and a manifest of the directory live in live.yaml
-when I run obnam backup metadata.yaml
+when I run obnam --config metadata.yaml backup
then backup generation is GEN
-when I invoke obnam restore metadata.yaml <GEN> rest
+when I invoke obnam --config metadata.yaml restore <GEN> rest
given a manifest of the directory live restored in rest in rest.yaml
then files live.yaml and rest.yaml match
~~~
@@ -869,9 +869,9 @@ and a client config based on metadata.yaml
and a file live/data.dat containing some random data
and symbolink link live/link that points at data.dat
and a manifest of the directory live in live.yaml
-when I run obnam backup metadata.yaml
+when I run obnam --config metadata.yaml backup
then backup generation is GEN
-when I invoke obnam restore metadata.yaml <GEN> rest
+when I invoke obnam --config metadata.yaml restore <GEN> rest
given a manifest of the directory live restored in rest in rest.yaml
then files live.yaml and rest.yaml match
~~~