summaryrefslogtreecommitdiff
path: root/yarns/9000-implements.yarn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-01-12 15:55:36 +0000
committerLars Wirzenius <liw@liw.fi>2014-01-12 15:55:36 +0000
commitd6863c3f7bb3fe019a7a71bfffe58fd532c0a5ab (patch)
treea66e490d090a35f1b44117b008ad6cf495beb8fc /yarns/9000-implements.yarn
parenta2b0154f4ac553a4b415abd43f7a9c973156ebbd (diff)
downloadobnam-d6863c3f7bb3fe019a7a71bfffe58fd532c0a5ab.tar.gz
Add scenario for remove-client
Diffstat (limited to 'yarns/9000-implements.yarn')
-rw-r--r--yarns/9000-implements.yarn20
1 files changed, 20 insertions, 0 deletions
diff --git a/yarns/9000-implements.yarn b/yarns/9000-implements.yarn
index 50a07453..06555a1f 100644
--- a/yarns/9000-implements.yarn
+++ b/yarns/9000-implements.yarn
@@ -241,6 +241,26 @@ Add a public key to a repository.
IMPLEMENTS WHEN user (\S+) adds key "(.+)" to repository (\S+)
run_obnam "$MATCH_1" -r "$DATADIR/$MATCH_3" add-key --keyid "$MATCH_2"
+Client management
+-----------------
+
+Sometimes, even if rarely, one wants to remove a complete client from
+a repository.
+
+ IMPLEMENTS WHEN user (\S+) removes user (\S+) from repository (\S+)
+ run_obnam "$MATCH_1" -r "$DATADIR/$MATCH_3" remove-client "$MATCH_2"
+
+After that, one wants to make sure the removed client isn't in the
+repository anymore.
+
+ IMPLEMENTS THEN user (\S+) can't see user (\S+) in repository (\S+)
+ if run_obnam "$MATCH_1" -r "$DATADIR/$MATCH_3" clients |
+ grep -x "$MATCH_2"
+ then
+ echo "Client $MATCH_2 still in repository $MATCH_3" 1>&2
+ exit 1
+ fi
+
Checks on results of an attempted operation
-------------------------------------------