[mesos] branch master updated: Documented EOF in ATTACH_CONTAINER_INPUT

[vi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

vinodkone pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mesos.git


The following commit(s) were added to refs/heads/master by this push:
     new 11bdb5f  Documented EOF in ATTACH_CONTAINER_INPUT
11bdb5f is described below

commit 11bdb5f996c8cfc94d325001cd0a861b654a08a4
Author: Bilal Amarni <bi...@gmail.com>
AuthorDate: Mon Jul 22 16:57:18 2019 +0200

    Documented EOF in ATTACH_CONTAINER_INPUT
    
    This documents how to indicate when EOF is reached on STDIN.
    
    See https://github.com/dcos/dcos-core-cli/blob/009999e1d8f4eddca5d961152f32669e02ed81d5/python/lib/dcos/dcos/mesos.py#L1657-L1658
---
 docs/operator-http-api.md | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/docs/operator-http-api.md b/docs/operator-http-api.md
index 2d4a9b6..1167838 100644
--- a/docs/operator-http-api.md
+++ b/docs/operator-http-api.md
@@ -3816,7 +3816,9 @@ they may contain subtypes of either DATA or CONTROL. DATA messages
 must be of type STDIN and contain the actual data to stream to the
 STDIN of the container being attached to. Currently, the only valid
 CONTROL message sends a heartbeat to keep the connection alive. We may
-add more CONTROL messages in the future.
+add more CONTROL messages in the future. An empty DATA message of type
+STDIN indicates EOF. If the container was launched with TTYInfo in their
+ContainerInfo, an EOT DATA message is expected instead.
 
 ```
 ATTACH_CONTAINER_INPUT HTTP Request (JSON):
@@ -3868,6 +3870,19 @@ Accept: application/json
       }
     }
   }
+}215
+{
+  "type": "ATTACH_CONTAINER_INPUT",
+  "attach_container_input": {
+    "type": "PROCESS_IO",
+    "process_io": {
+      "type": "DATA",
+      "data": {
+        "type": "STDIN",
+        "data": ""
+      }
+    }
+  }
 }
 ...