From cb27bff054839c706304214a686579d893f97c2f Mon Sep 17 00:00:00 2001 From: juanvallejo Date: Thu, 1 Dec 2016 11:15:04 -0500 Subject: [PATCH] update generated docs --- docs/man/man1/oc-new-app.1 | 4 ++-- docs/man/man1/oc-new-build.1 | 4 ++-- docs/man/man1/oc-process.1 | 8 ++++---- docs/man/man1/oc-start-build.1 | 9 +-------- docs/man/man1/openshift-cli-new-app.1 | 4 ++-- docs/man/man1/openshift-cli-new-build.1 | 4 ++-- docs/man/man1/openshift-cli-process.1 | 8 ++++---- docs/man/man1/openshift-cli-start-build.1 | 9 +-------- 8 files changed, 18 insertions(+), 32 deletions(-) diff --git a/docs/man/man1/oc-new-app.1 b/docs/man/man1/oc-new-app.1 index 9847d6be9326..fddea97cc790 100644 --- a/docs/man/man1/oc-new-app.1 +++ b/docs/man/man1/oc-new-app.1 @@ -115,8 +115,8 @@ If you provide source code, a new build will be automatically triggered. You can Search all templates, image streams, and Docker images that match the arguments provided. .PP -\fB\-\-strategy\fP= - Specify the build strategy to use if you don't want to detect (docker|pipeline|source). +\fB\-\-strategy\fP="" + Specify the build strategy to use if you don't want to detect (docker|source). .PP \fB\-\-template\fP=[] diff --git a/docs/man/man1/oc-new-build.1 b/docs/man/man1/oc-new-build.1 index ff6d83bb0bdb..2a22c93cbecb 100644 --- a/docs/man/man1/oc-new-build.1 +++ b/docs/man/man1/oc-new-build.1 @@ -103,8 +103,8 @@ Once the build configuration is created a new build will be automatically trigge Specify the file or directory to copy from the source image and its destination in the build directory. Format: [source]:[destination\-dir]. .PP -\fB\-\-strategy\fP= - Specify the build strategy to use if you don't want to detect (docker|pipeline|source). +\fB\-\-strategy\fP="" + Specify the build strategy to use if you don't want to detect (docker|source). .PP \fB\-\-to\fP="" diff --git a/docs/man/man1/oc-process.1 b/docs/man/man1/oc-process.1 index f19e3b69b02e..2afd14bd4715 100644 --- a/docs/man/man1/oc-process.1 +++ b/docs/man/man1/oc-process.1 @@ -39,10 +39,6 @@ The output of the process command is always a list of one or more resources. You \fB\-\-output\-version\fP="" Output the formatted object with the given version (default api\-version). -.PP -\fB\-p\fP, \fB\-\-param\fP=[] - Specify a key\-value pair (eg. \-p FOO=BAR) to set/override a parameter value in the template. - .PP \fB\-\-parameters\fP=false Do not process but only print available parameters @@ -56,6 +52,10 @@ The output of the process command is always a list of one or more resources. You Template string or path to template file to use when \-o=template or \-o=templatefile. The template format is golang templates [ \[la]http://golang.org/pkg/text/template/#pkg-overview\[ra]] +.PP +\fB\-v\fP, \fB\-\-value\fP=[] + Specify a key\-value pair (eg. \-v FOO=BAR) to set/override a parameter value in the template. + .SH OPTIONS INHERITED FROM PARENT COMMANDS .PP diff --git a/docs/man/man1/oc-start-build.1 b/docs/man/man1/oc-start-build.1 index 132092b5fdcd..b42758966fd7 100644 --- a/docs/man/man1/oc-start-build.1 +++ b/docs/man/man1/oc-start-build.1 @@ -19,10 +19,7 @@ Start a build This command starts a new build for the provided build config or copies an existing build using \-\-from\-build= . Pass the \-\-follow flag to see output from the build. .PP -In addition, you can pass a file, directory, or source code repository with the \-\-from\-file, \-\-from\-dir, or \-\-from\-repo flags directly to the build. The contents will be streamed to the build and override the current build source settings. When using \-\-from\-repo, the \-\-commit flag can be used to control which branch, tag, or commit is sent to the server. If you pass \-\-from\-file, the file is placed in the root of an empty directory with the same filename. It is also possible to pass a http or https url to \-\-from\-file and \-\-from\-archive, however authentication is not supported and in case of https the certificate must be valid and recognized by your system. - -.PP -Note that builds triggered from binary input will not preserve the source on the server, so rebuilds triggered by base image changes will use the source specified on the build config. +In addition, you can pass a file, directory, or source code repository with the \-\-from\-file, \-\-from\-dir, or \-\-from\-repo flags directly to the build. The contents will be streamed to the build and override the current build source settings. When using \-\-from\-repo, the \-\-commit flag can be used to control which branch, tag, or commit is sent to the server. If you pass \-\-from\-file, the file is placed in the root of an empty directory with the same filename. Note that builds triggered from binary input will not preserve the source on the server, so rebuilds triggered by base image changes will use the source specified on the build config. .SH OPTIONS @@ -42,10 +39,6 @@ Note that builds triggered from binary input will not preserve the source on the \fB\-F\fP, \fB\-\-follow\fP=false Start a build and watch its logs until it completes or fails -.PP -\fB\-\-from\-archive\fP="" - An archive (tar, tar.gz, zip) to be extracted before the build and used as the binary input. - .PP \fB\-\-from\-build\fP="" Specify the name of a build which should be re\-run diff --git a/docs/man/man1/openshift-cli-new-app.1 b/docs/man/man1/openshift-cli-new-app.1 index 4c9421c9ae98..366fa7c79355 100644 --- a/docs/man/man1/openshift-cli-new-app.1 +++ b/docs/man/man1/openshift-cli-new-app.1 @@ -115,8 +115,8 @@ If you provide source code, a new build will be automatically triggered. You can Search all templates, image streams, and Docker images that match the arguments provided. .PP -\fB\-\-strategy\fP= - Specify the build strategy to use if you don't want to detect (docker|pipeline|source). +\fB\-\-strategy\fP="" + Specify the build strategy to use if you don't want to detect (docker|source). .PP \fB\-\-template\fP=[] diff --git a/docs/man/man1/openshift-cli-new-build.1 b/docs/man/man1/openshift-cli-new-build.1 index 891dc4ceff19..ab0cef634c2c 100644 --- a/docs/man/man1/openshift-cli-new-build.1 +++ b/docs/man/man1/openshift-cli-new-build.1 @@ -103,8 +103,8 @@ Once the build configuration is created a new build will be automatically trigge Specify the file or directory to copy from the source image and its destination in the build directory. Format: [source]:[destination\-dir]. .PP -\fB\-\-strategy\fP= - Specify the build strategy to use if you don't want to detect (docker|pipeline|source). +\fB\-\-strategy\fP="" + Specify the build strategy to use if you don't want to detect (docker|source). .PP \fB\-\-to\fP="" diff --git a/docs/man/man1/openshift-cli-process.1 b/docs/man/man1/openshift-cli-process.1 index 36f0dbbcb566..570437d6e293 100644 --- a/docs/man/man1/openshift-cli-process.1 +++ b/docs/man/man1/openshift-cli-process.1 @@ -39,10 +39,6 @@ The output of the process command is always a list of one or more resources. You \fB\-\-output\-version\fP="" Output the formatted object with the given version (default api\-version). -.PP -\fB\-p\fP, \fB\-\-param\fP=[] - Specify a key\-value pair (eg. \-p FOO=BAR) to set/override a parameter value in the template. - .PP \fB\-\-parameters\fP=false Do not process but only print available parameters @@ -56,6 +52,10 @@ The output of the process command is always a list of one or more resources. You Template string or path to template file to use when \-o=template or \-o=templatefile. The template format is golang templates [ \[la]http://golang.org/pkg/text/template/#pkg-overview\[ra]] +.PP +\fB\-v\fP, \fB\-\-value\fP=[] + Specify a key\-value pair (eg. \-v FOO=BAR) to set/override a parameter value in the template. + .SH OPTIONS INHERITED FROM PARENT COMMANDS .PP diff --git a/docs/man/man1/openshift-cli-start-build.1 b/docs/man/man1/openshift-cli-start-build.1 index 38dda9a5ddc9..c406c187bc61 100644 --- a/docs/man/man1/openshift-cli-start-build.1 +++ b/docs/man/man1/openshift-cli-start-build.1 @@ -19,10 +19,7 @@ Start a build This command starts a new build for the provided build config or copies an existing build using \-\-from\-build= . Pass the \-\-follow flag to see output from the build. .PP -In addition, you can pass a file, directory, or source code repository with the \-\-from\-file, \-\-from\-dir, or \-\-from\-repo flags directly to the build. The contents will be streamed to the build and override the current build source settings. When using \-\-from\-repo, the \-\-commit flag can be used to control which branch, tag, or commit is sent to the server. If you pass \-\-from\-file, the file is placed in the root of an empty directory with the same filename. It is also possible to pass a http or https url to \-\-from\-file and \-\-from\-archive, however authentication is not supported and in case of https the certificate must be valid and recognized by your system. - -.PP -Note that builds triggered from binary input will not preserve the source on the server, so rebuilds triggered by base image changes will use the source specified on the build config. +In addition, you can pass a file, directory, or source code repository with the \-\-from\-file, \-\-from\-dir, or \-\-from\-repo flags directly to the build. The contents will be streamed to the build and override the current build source settings. When using \-\-from\-repo, the \-\-commit flag can be used to control which branch, tag, or commit is sent to the server. If you pass \-\-from\-file, the file is placed in the root of an empty directory with the same filename. Note that builds triggered from binary input will not preserve the source on the server, so rebuilds triggered by base image changes will use the source specified on the build config. .SH OPTIONS @@ -42,10 +39,6 @@ Note that builds triggered from binary input will not preserve the source on the \fB\-F\fP, \fB\-\-follow\fP=false Start a build and watch its logs until it completes or fails -.PP -\fB\-\-from\-archive\fP="" - An archive (tar, tar.gz, zip) to be extracted before the build and used as the binary input. - .PP \fB\-\-from\-build\fP="" Specify the name of a build which should be re\-run