Browse code

Update docs wrt multiple --env/--param arguments

The following syntax is not supported anymore:

--env K1=V1,K2=V2,...
--param K1=V1,K2=V2,...

Martin Milata authored on 2016/12/13 00:48:27
Showing 2 changed files
... ...
@@ -104,7 +104,7 @@ The options are:
104 104
 |`--code` *dir*                | Use source code in *dir*                           |
105 105
 |`--context-dir` *dir*         | Use *dir* as context dir in the build              |
106 106
 |`--docker-image` *image*      | Include Docker image *image* in the app            |
107
-|`--env` (`-e`) *k1=v1,...*    | Set env vars *k1...* to values *v1...*             |
107
+|`--env` (`-e`) *k=v*          | Set env var *k* to value *v*                       |
108 108
 |`--file` *filename*           | Use template in *filename*                         |
109 109
 |`--group` *comp1*`+`*comp2*   | Group together components *comp1* and *comp2*      |
110 110
 |`--image-stream` (`-i`) *is*  | Use imagestream *is* in the app                    |
... ...
@@ -115,7 +115,7 @@ The options are:
115 115
 |`--output-template` *s*       | Template string (`-o template`) or path (`-o templatefile`) |
116 116
 |`--output-version` *version*  | Output with *version* (default api-version)        |
117 117
 |`--output` (`-o`) *format*    | *format* is one of: `json`, `yaml`, `template`, `templatefile` |
118
-|`--param` (`-p`) *k1=v1,...*  | Set/override parameters *k1...* with *v1...*       |
118
+|`--param` (`-p`) *k=v*        | Set/override parameter *k* with value *v*          |
119 119
 |`--strategy` *s*              | Use build strategy *s*, one of: `docker`, `source` |
120 120
 |`--template` *t*              | Use OpenShift stored template *t* in the app       |
121 121
 
... ...
@@ -160,7 +160,7 @@ Other options:
160 160
 
161 161
 | Name       |  Description                                                                                             |
162 162
 |:-----------|:---------------------------------------------------------------------------------------------------------|
163
-|`--env`, *(-e)* FOO=bar | Explicitly set or override environment variables for the current build. Does not change the BuildConfig. |
163
+|`--env`, *(-e)* FOO=bar | Explicitly set or override environment variable for the current build. Does not change the BuildConfig. |
164 164
 |`--build-loglevel` | Set or override the build log level output [0-5] during the build. |
165 165
 |`--commit`  | Specify the source code commit identifier the build should use; requires a build based on a Git repository. |
166 166
 |`--follow`  | Start a build and watch its logs until it completes or fails. |
... ...
@@ -172,7 +172,7 @@ In case you need additional control over how flags behave in terms of code compl
172 172
 |=======
173 173
 |`cmd.MarkFlagFilename("my-flag-name")`                 |allows the given flag to autocomplete as a path to file or directory.
174 174
 |`cmd.MarkFlagFilename("my-flag-name", "yaml", "yml")`  |consider the given file extensions when doing autocomplete.
175
-|`MarkFlagRequired("my-flag-name")`                     |mark a flag as required. 
175
+|`cmd.MarkFlagRequired("my-flag-name")`                 |mark a flag as required.
176 176
 |=======
177 177
 
178 178
 === Automatically Generated Documentation