Update: yarn scenarios to use named pipelines

1 files changed, 12 insertions, 10 deletions

diff --git a/yarns/500-build-fail.yarn b/yarns/500-build-fail.yarn
index 2f5d79c..f0afa32 100644
--- a/yarns/500-build-fail.yarn
+++ b/yarns/500-build-fail.yarn
@@ -29,6 +29,7 @@ Set up the controller.
     GIVEN an RSA key pair for token signing
     AND controller config uses statedir at the state directory
     AND an access token for user with scopes
+    ... uapi_pipelines_post
     ... uapi_projects_post
     ... uapi_projects_id_pipelines_id_put
     ... uapi_projects_id_pipelines_id_get
@@ -39,20 +40,21 @@ Set up the controller.
     ... uapi_logs_id_get
     AND a running ick controller
 
-Add up a project.
+Add up a project and its pipelines.
 
+    WHEN user makes request POST /pipelines with a valid token and body
+    ... {
+    ...     "name": "construct",
+    ...     "actions": [
+    ...         { "shell": "day 1" },
+    ...         { "shell": "day 2" }
+    ...     ]
+    ... }
+    THEN result has status code 201
     WHEN user makes request POST /projects with a valid token and body
     ... {
     ...     "project": "rome",
-    ...     "pipelines": [
-    ...         {
-    ...             "name": "construct",
-    ...             "actions": [
-    ...                 { "shell": "day 1" },
-    ...                 { "shell": "day 2" }
-    ...             ]
-    ...         }
-    ...     ]
+    ...     "pipelines": ["construct"]
     ... }
     THEN result has status code 201