From c6ce6faab75ea291d85e5780b95cccc255a15c2a Mon Sep 17 00:00:00 2001
From: Lars Wirzenius <liw@liw.fi>
Date: Mon, 6 Nov 2017 14:07:58 +0100
Subject: Change: /log to /logs, for consistency

---
 yarns/400-build.yarn | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

(limited to 'yarns/400-build.yarn')

diff --git a/yarns/400-build.yarn b/yarns/400-build.yarn
index c57fd07..44e01f3 100644
--- a/yarns/400-build.yarn
+++ b/yarns/400-build.yarn
@@ -35,7 +35,7 @@ Set up the controller.
     ... uapi_workers_id_get
     ... uapi_builds_get
     ... uapi_builds_id_get
-    ... uapi_log_id_get
+    ... uapi_logs_id_get
     AND a running ick controller
 
 Add up a project.
@@ -95,7 +95,7 @@ be in the path or can we get it in the access token?**
     AND body matches
     ... {
     ...     "build_id": 1,
-    ...     "log": "/log/1",
+    ...     "log": "/logs/1",
     ...     "worker": "obelix",
     ...     "project": "rome",
     ...     "pipeline": "construct",
@@ -110,7 +110,7 @@ be in the path or can we get it in the access token?**
     AND body matches
     ... {
     ...     "build_id": 1,
-    ...     "log": "/log/1",
+    ...     "log": "/logs/1",
     ...     "worker": "obelix",
     ...     "project": "rome",
     ...     "pipeline": "construct",
@@ -136,7 +136,7 @@ User can now see pipeline is running and which worker is building it.
     ...     "worker": "obelix",
     ...     "doing": {
     ...         "build_id": 1,
-    ...         "log": "/log/1",
+    ...         "log": "/logs/1",
     ...         "worker": "obelix",
     ...         "project": "rome",
     ...         "pipeline": "construct",
@@ -154,17 +154,17 @@ User can now see pipeline is running and which worker is building it.
     ...     "builds": [
     ...         {
     ...             "build_id": 1,
-    ...             "log": "/log/1",
+    ...             "log": "/logs/1",
     ...             "worker": "obelix",
     ...             "project": "rome",
     ...             "pipeline": "construct",
     ...             "status": "building",
-    ...             "log": "/log/1"
+    ...             "log": "/logs/1"
     ...         }
     ...     ]
     ... }
 
-    WHEN user makes request GET /log/1
+    WHEN user makes request GET /logs/1
     THEN result has status code 200
     AND result has header Content-Type: text/plain
     AND body text is ""
@@ -191,7 +191,7 @@ Still the same job, since the first build step didnt't finish.
     AND body matches
     ... {
     ...     "build_id": 1,
-    ...     "log": "/log/1",
+    ...     "log": "/logs/1",
     ...     "worker": "obelix",
     ...     "project": "rome",
     ...     "pipeline": "construct",
@@ -203,7 +203,7 @@ Still the same job, since the first build step didnt't finish.
 
 The build log is immediately accessible.
 
-    WHEN user makes request GET /log/1
+    WHEN user makes request GET /logs/1
     THEN result has status code 200
     AND result has header Content-Type: text/plain
     AND body text is "hey ho"
@@ -223,7 +223,7 @@ Report the step is done, and successfully.
     ... }
     THEN result has status code 201
 
-    WHEN user makes request GET /log/1
+    WHEN user makes request GET /logs/1
     THEN result has status code 200
     AND result has header Content-Type: text/plain
     AND body text is "hey ho, hey ho\n"
@@ -235,7 +235,7 @@ Now there's another step to do.
     AND body matches
     ... {
     ...     "build_id": 1,
-    ...     "log": "/log/1",
+    ...     "log": "/logs/1",
     ...     "worker": "obelix",
     ...     "project": "rome",
     ...     "pipeline": "construct",
@@ -261,7 +261,7 @@ User sees changed status.
     ...         "step": {
     ...             "shell": "day 2"
     ...         },
-    ...         "log": "/log/1"
+    ...         "log": "/logs/1"
     ...     }
     ... }
 
@@ -301,12 +301,12 @@ Also, there's a build with a log.
     ...     "builds": [
     ...         {
     ...             "build_id": 1,
-    ...             "log": "/log/1",
+    ...             "log": "/logs/1",
     ...             "worker": "obelix",
     ...             "project": "rome",
     ...             "pipeline": "construct",
     ...             "status": 0,
-    ...             "log": "/log/1"
+    ...             "log": "/logs/1"
     ...         }
     ...     ]
     ... }
@@ -316,15 +316,15 @@ Also, there's a build with a log.
     AND body matches
     ... {
     ...     "build_id": 1,
-    ...     "log": "/log/1",
+    ...     "log": "/logs/1",
     ...     "worker": "obelix",
     ...     "project": "rome",
     ...     "pipeline": "construct",
     ...     "status": 0,
-    ...     "log": "/log/1"
+    ...     "log": "/logs/1"
     ... }
 
-    WHEN user makes request GET /log/1
+    WHEN user makes request GET /logs/1
     THEN result has status code 200
     AND result has header Content-Type: text/plain
     AND body text is "hey ho, hey ho\nto the gold mine we go!\n"
-- 
cgit v1.2.1