Browse code

update invalid oc extract usage flag to "keys"

juanvallejo authored on 2016/08/25 02:06:39
Showing 3 changed files
... ...
@@ -21,7 +21,7 @@ Each key in the config map or secret is created as a separate file with the name
21 21
 is when you mount a secret or config map into a container.
22 22
 
23 23
 .PP
24
-You can limit which keys are extracted with the \-\-only=NAME flag, or set the directory to extract to
24
+You can limit which keys are extracted with the \-\-keys=NAME flag, or set the directory to extract to
25 25
 with \-\-to=DIRECTORY.
26 26
 
27 27
 
... ...
@@ -21,7 +21,7 @@ Each key in the config map or secret is created as a separate file with the name
21 21
 is when you mount a secret or config map into a container.
22 22
 
23 23
 .PP
24
-You can limit which keys are extracted with the \-\-only=NAME flag, or set the directory to extract to
24
+You can limit which keys are extracted with the \-\-keys=NAME flag, or set the directory to extract to
25 25
 with \-\-to=DIRECTORY.
26 26
 
27 27
 
... ...
@@ -28,7 +28,7 @@ The extract command makes it easy to download the contents of a config map or se
28 28
 Each key in the config map or secret is created as a separate file with the name of the key, as it
29 29
 is when you mount a secret or config map into a container.
30 30
 
31
-You can limit which keys are extracted with the --only=NAME flag, or set the directory to extract to
31
+You can limit which keys are extracted with the --keys=NAME flag, or set the directory to extract to
32 32
 with --to=DIRECTORY.`
33 33
 
34 34
 	extractExample = `  # extract the secret "test" to the current directory