From c64c396174f169dab21622dca0fa289c86d9765a Mon Sep 17 00:00:00 2001 From: allencloud Date: Thu, 9 Mar 2017 15:31:10 +0800 Subject: [PATCH] move secret into swarm thing in swagger Signed-off-by: allencloud Upstream-commit: 6918624985e4859e44404b06a01e86639dcaa900 Component: engine --- components/engine/api/swagger.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/components/engine/api/swagger.yaml b/components/engine/api/swagger.yaml index b59888c17b..4a99112c65 100644 --- a/components/engine/api/swagger.yaml +++ b/components/engine/api/swagger.yaml @@ -118,8 +118,6 @@ tags: Run new commands inside running containers. See the [command-line reference](https://docs.docker.com/engine/reference/commandline/exec/) for more information. To exec a command in a container, you first need to create an exec instance, then start it. These two API endpoints are wrapped up in a single command-line command, `docker exec`. - - name: "Secret" - x-displayName: "Secrets" # Swarm things - name: "Swarm" x-displayName: "Swarm" @@ -137,6 +135,10 @@ tags: x-displayName: "Tasks" description: | A task is a container running on a swarm. It is the atomic scheduling unit of swarm. Swarm mode must be enabled for these endpoints to work. + - name: "Secret" + x-displayName: "Secrets" + description: | + Secrets are sensitive data that can be used by services. Swarm mode must be enabled for these endpoints to work. # System things - name: "Plugin" x-displayName: "Plugins"