From ab225178a7c63ddaf66f344ac39efacef7e1abcb Mon Sep 17 00:00:00 2001
From: Reed Allman <rdallman10@gmail.com>
Date: Thu, 4 Jan 2018 15:03:58 -0600
Subject: [PATCH] revert swagger to json for logs (#639)

we need to keep it like this until we move to swagger 3, so that we don't
break clients using old versions of fn and new clients.
---
 docs/swagger.yml | 23 ++++++++++++++++++++---
 1 file changed, 20 insertions(+), 3 deletions(-)

diff --git a/docs/swagger.yml b/docs/swagger.yml
index 825cf3c4c..672fda415 100644
--- a/docs/swagger.yml
+++ b/docs/swagger.yml
@@ -2,7 +2,7 @@ swagger: '2.0'
 info:
   title: fn
   description: The open source serverless platform.
-  version: "0.2.3"
+  version: "0.2.4"
 # the domain of the service
 host: "127.0.0.1:8080"
 # array of all schemes that your API supports
@@ -371,7 +371,6 @@ paths:
       tags:
         - Call
         - Log
-      produces: ['text/plain',]
       parameters:
         - name: app
           description: App Name
@@ -387,7 +386,7 @@ paths:
         200:
           description: Log found
           schema:
-            type: string
+            $ref:  '#/definitions/LogWrapper'
         404:
           description: Log not found.
           schema:
@@ -637,6 +636,24 @@ definitions:
         $ref: '#/definitions/Call'
         description: "Call object."
 
+  LogWrapper:
+    type: object
+    required:
+      - log
+    properties:
+      log:
+        $ref: '#/definitions/Log'
+        description: "Call log entry."
+
+  Log:
+    type: object
+    properties:
+      call_id:
+        type: string
+        description: Call UUID ID
+      log:
+        type: string # maybe bytes, long logs wouldn't fit into string type
+
   Call:
     type: object
     properties: