upgrading cobra

Signed-off-by: bryanl <bryanliles@gmail.com>

docs/cli-reference/ks_pkg.md

@@ -5,7 +5,6 @@ Manage packages and dependencies for the current ksonnet application
 ### Synopsis
 
 
-
 A ksonnet package contains:
 
 * A set of prototypes (see `ks prototype --help` for more info on prototypes), which
@@ -33,7 +32,13 @@ See the annotated file tree below, as an example:
 
 
 ```
-ks pkg
+ks pkg [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for pkg
 ```
 
 ### Options inherited from parent commands
@@ -43,6 +48,7 @@ ks pkg
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 * [ks pkg describe](ks_pkg_describe.md)	 - Describe a ksonnet package and its contents
 * [ks pkg install](ks_pkg_install.md)	 - Install a package (e.g. extra prototypes) for the current ksonnet app

docs/cli-reference/ks_pkg_describe.md

@@ -5,7 +5,6 @@ Describe a ksonnet package and its contents
 ### Synopsis
 
 
-
 The `describe` command outputs documentation for a package that is available
 (e.g. downloaded) in the current ksonnet application. (This must belong to an already
 known `<registry-name>` like *incubator*). The output includes:
@@ -24,7 +23,13 @@ known `<registry-name>` like *incubator*). The output includes:
 
 
 ```
-ks pkg describe [<registry-name>/]<package-name>
+ks pkg describe [<registry-name>/]<package-name> [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for describe
 ```
 
 ### Options inherited from parent commands
@@ -34,5 +39,6 @@ ks pkg describe [<registry-name>/]<package-name>
 ```
 
 ### SEE ALSO
+
 * [ks pkg](ks_pkg.md)	 - Manage packages and dependencies for the current ksonnet application
 

docs/cli-reference/ks_pkg_install.md

@@ -5,7 +5,6 @@ Install a package (e.g. extra prototypes) for the current ksonnet app
 ### Synopsis
 
 
-
 The `install` command caches a ksonnet library locally, and makes it available
 for use in the current ksonnet application. Enough info and metadata is recorded in
 `app.yaml` that new users can retrieve the dependency after a fresh clone of this app.
@@ -24,7 +23,7 @@ channels for official ksonnet libraries.
 
 
 ```
-ks pkg install <registry>/<library>@<version>
+ks pkg install <registry>/<library>@<version> [flags]
 ```
 
 ### Examples
@@ -46,6 +45,7 @@ ks pkg install incubator/nginx@master
 ### Options
 
 ```
+  -h, --help          help for install
       --name string   Name to give the dependency, to use within the ksonnet app
 ```
 
@@ -56,5 +56,6 @@ ks pkg install incubator/nginx@master
 ```
 
 ### SEE ALSO
+
 * [ks pkg](ks_pkg.md)	 - Manage packages and dependencies for the current ksonnet application
 

docs/cli-reference/ks_pkg_list.md

@@ -5,7 +5,6 @@ List all packages known (downloaded or not) for the current ksonnet app
 ### Synopsis
 
 
-
 The `list` command outputs a table that describes all *known* packages (not
 necessarily downloaded, but available from existing registries). This includes
 the following info:
@@ -24,7 +23,13 @@ the following info:
 
 
 ```
-ks pkg list
+ks pkg list [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for list
 ```
 
 ### Options inherited from parent commands
@@ -34,5 +39,6 @@ ks pkg list
 ```
 
 ### SEE ALSO
+
 * [ks pkg](ks_pkg.md)	 - Manage packages and dependencies for the current ksonnet application
 

docs/cli-reference/ks_prototype.md

@@ -5,7 +5,6 @@ Instantiate, inspect, and get examples for ksonnet prototypes
 ### Synopsis
 
 
-
 Use the `prototype` subcommands to manage, inspect, instantiate, and get
 examples for ksonnet prototypes.
 
@@ -23,7 +22,13 @@ for your use case.
 
 
 ```
-ks prototype
+ks prototype [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for prototype
 ```
 
 ### Options inherited from parent commands
@@ -33,6 +38,7 @@ ks prototype
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 * [ks prototype describe](ks_prototype_describe.md)	 - See more info about a prototype's output and usage
 * [ks prototype list](ks_prototype_list.md)	 - List all locally available ksonnet prototypes

docs/cli-reference/ks_prototype_describe.md

@@ -5,7 +5,6 @@ See more info about a prototype's output and usage
 ### Synopsis
 
 
-
 This command outputs documentation, examples, and other information for
 the specified prototype (identified by name). Specifically, this describes:
 
@@ -23,7 +22,7 @@ the specified prototype (identified by name). Specifically, this describes:
 
 
 ```
-ks prototype describe <prototype-name>
+ks prototype describe <prototype-name> [flags]
 ```
 
 ### Examples
@@ -34,6 +33,12 @@ ks prototype describe <prototype-name>
 ks prototype describe deployment
 ```
 
+### Options
+
+```
+  -h, --help   help for describe
+```
+
 ### Options inherited from parent commands
 
 ```
@@ -41,5 +46,6 @@ ks prototype describe deployment
 ```
 
 ### SEE ALSO
+
 * [ks prototype](ks_prototype.md)	 - Instantiate, inspect, and get examples for ksonnet prototypes
 

docs/cli-reference/ks_prototype_list.md

@@ -5,7 +5,6 @@ List all locally available ksonnet prototypes
 ### Synopsis
 
 
-
 The `list` command displays all prototypes that are available locally, as
 well as brief descriptions of what they generate.
 
@@ -25,7 +24,13 @@ from the *incubator* registry.
 
 
 ```
-ks prototype list
+ks prototype list [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for list
 ```
 
 ### Options inherited from parent commands
@@ -35,5 +40,6 @@ ks prototype list
 ```
 
 ### SEE ALSO
+
 * [ks prototype](ks_prototype.md)	 - Instantiate, inspect, and get examples for ksonnet prototypes
 

docs/cli-reference/ks_prototype_preview.md

@@ -5,7 +5,6 @@ Preview a prototype's output without creating a component (stdout)
 ### Synopsis
 
 
-
 This `preview` command expands a prototype with CLI flag parameters, and
 emits the resulting manifest to stdout. This allows you to see the potential
 output of a `ks generate` command without actually creating a new component file.
@@ -21,7 +20,7 @@ a component with `ks generate` and then use `ks show`.
 
 
 ```
-ks prototype preview <prototype-name> [parameter-flags]
+ks prototype preview <prototype-name> [parameter-flags] [flags]
 ```
 
 ### Examples
@@ -36,6 +35,12 @@ ks prototype preview single-port-deployment \
   --port=80
 ```
 
+### Options
+
+```
+  -h, --help   help for preview
+```
+
 ### Options inherited from parent commands
 
 ```
@@ -43,5 +48,6 @@ ks prototype preview single-port-deployment \
 ```
 
 ### SEE ALSO
+
 * [ks prototype](ks_prototype.md)	 - Instantiate, inspect, and get examples for ksonnet prototypes
 

docs/cli-reference/ks_prototype_search.md

@@ -5,7 +5,6 @@ Search for a prototype
 ### Synopsis
 
 
-
 The `prototype search` command allows you to search for specific prototypes by name.
 Specifically, it matches any prototypes with names that contain the string <name-substring>.
 
@@ -18,7 +17,7 @@ Specifically, it matches any prototypes with names that contain the string <name
 
 
 ```
-ks prototype search <name-substring>
+ks prototype search <name-substring> [flags]
 ```
 
 ### Examples
@@ -29,6 +28,12 @@ ks prototype search <name-substring>
 ks prototype search service
 ```
 
+### Options
+
+```
+  -h, --help   help for search
+```
+
 ### Options inherited from parent commands
 
 ```
@@ -36,5 +41,6 @@ ks prototype search service
 ```
 
 ### SEE ALSO
+
 * [ks prototype](ks_prototype.md)	 - Instantiate, inspect, and get examples for ksonnet prototypes
 

docs/cli-reference/ks_prototype_use.md

@@ -5,7 +5,6 @@ Use the specified prototype to generate a component manifest
 ### Synopsis
 
 
-
 The `generate` command (aliased from `prototype use`) generates Kubernetes-
 compatible, Jsonnet manifests for components in your ksonnet app. Each component
 corresponds to a single manifest in the `components/` directory. This manifest
@@ -43,7 +42,7 @@ different prototypes support their own unique flags.
 
 
 ```
-ks prototype use <prototype-name> <componentName> [type] [parameter-flags]
+ks prototype use <prototype-name> <componentName> [type] [parameter-flags] [flags]
 ```
 
 ### Examples
@@ -68,6 +67,12 @@ ks prototype use deployment nginx-depl \
   --image=nginx
 ```
 
+### Options
+
+```
+  -h, --help   help for use
+```
+
 ### Options inherited from parent commands
 
 ```
@@ -75,5 +80,6 @@ ks prototype use deployment nginx-depl \
 ```
 
 ### SEE ALSO
+
 * [ks prototype](ks_prototype.md)	 - Instantiate, inspect, and get examples for ksonnet prototypes
 

docs/cli-reference/ks_registry.md

@@ -5,7 +5,6 @@ Manage registries for current project
 ### Synopsis
 
 
-
 A ksonnet registry is basically a repository for *packages*. (Registry here is
 used in the same sense as a container image registry). Registries are identified
 by a `registry.yaml` in their root that declares which packages they contain.
@@ -24,7 +23,13 @@ described above. (See `ks prototype --help` for more information.)
 
 
 ```
-ks registry
+ks registry [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for registry
 ```
 
 ### Options inherited from parent commands
@@ -34,6 +39,7 @@ ks registry
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 * [ks registry add](ks_registry_add.md)	 - Add a registry to the current ksonnet app
 * [ks registry describe](ks_registry_describe.md)	 - Describe a ksonnet registry and the packages it contains

docs/cli-reference/ks_registry_add.md

@@ -5,7 +5,6 @@ Add a registry to the current ksonnet app
 ### Synopsis
 
 
-
 The `add` command allows custom registries to be added to your ksonnet app,
 provided that their file structures follow the appropriate schema. *You can look
 at the `incubator` repo (https://github.com/ksonnet/parts/tree/master/incubator)
@@ -31,7 +30,7 @@ name*). If a version is not specified, it will default to `latest`.
 
 
 ```
-ks registry add <registry-name> <registry-uri>
+ks registry add <registry-name> <registry-uri> [flags]
 ```
 
 ### Examples
@@ -49,6 +48,7 @@ ks registry add databases github.com/example/tree/master/reg --version=0.0.1
 ### Options
 
 ```
+  -h, --help             help for add
       --version string   Version of the registry to add
 ```
 
@@ -59,5 +59,6 @@ ks registry add databases github.com/example/tree/master/reg --version=0.0.1
 ```
 
 ### SEE ALSO
+
 * [ks registry](ks_registry.md)	 - Manage registries for current project
 

docs/cli-reference/ks_registry_describe.md

@@ -5,7 +5,6 @@ Describe a ksonnet registry and the packages it contains
 ### Synopsis
 
 
-
 The `describe` command outputs documentation for the ksonnet registry identified
 by `<registry-name>`. Specifically, it displays the following:
 
@@ -21,7 +20,13 @@ by `<registry-name>`. Specifically, it displays the following:
 
 
 ```
-ks registry describe <registry-name>
+ks registry describe <registry-name> [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for describe
 ```
 
 ### Options inherited from parent commands
@@ -31,5 +36,6 @@ ks registry describe <registry-name>
 ```
 
 ### SEE ALSO
+
 * [ks registry](ks_registry.md)	 - Manage registries for current project
 

docs/cli-reference/ks_registry_list.md

@@ -5,7 +5,6 @@ List all registries known to the current ksonnet app.
 ### Synopsis
 
 
-
 The `list` command displays all known ksonnet registries in a table. This
 table includes the following info:
 
@@ -21,7 +20,13 @@ table includes the following info:
 
 
 ```
-ks registry list
+ks registry list [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for list
 ```
 
 ### Options inherited from parent commands
@@ -31,5 +36,6 @@ ks registry list
 ```
 
 ### SEE ALSO
+
 * [ks registry](ks_registry.md)	 - Manage registries for current project
 

docs/cli-reference/ks_show.md

@@ -5,7 +5,6 @@ Show expanded manifests for a specific environment.
 ### Synopsis
 
 
-
 Show expanded manifests (resource definitions) for a specific environment.
 Jsonnet manifests, each defining a ksonnet component, are expanded into their
 JSON or YAML equivalents (YAML is the default). Any parameters in these Jsonnet
@@ -28,7 +27,7 @@ manifest for that particular component.
 
 
 ```
-ks show <env> [-c <component-filename>]
+ks show <env> [-c <component-filename>] [flags]
 ```
 
 ### Examples
@@ -54,6 +53,7 @@ ks show dev -c redis -c nginx-server
   -V, --ext-str stringSlice           Values of external variables
       --ext-str-file stringSlice      Read external variable from a file
   -o, --format string                 Output format.  Supported values are: json, yaml (default "yaml")
+  -h, --help                          help for show
   -J, --jpath stringSlice             Additional jsonnet library search path
       --resolve-images string         Change implementation of resolveImage native function. One of: noop, registry (default "noop")
       --resolve-images-error string   Action when resolveImage fails. One of ignore,warn,error (default "warn")
@@ -68,5 +68,6 @@ ks show dev -c redis -c nginx-server
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 

docs/cli-reference/ks_validate.md

@@ -5,7 +5,6 @@ Check generated component manifests against the server's API
 ### Synopsis
 
 
-
 The `validate` command checks that an application or file is compliant with the
 server API's Kubernetes specification. Note that this command actually communicates
 *with* the server for the specified `<env-name>`, so it only works if your
@@ -27,7 +26,7 @@ the manifest for that particular component.
 
 
 ```
-ks validate <env-name> [-c <component-name>]
+ks validate <env-name> [-c <component-name>] [flags]
 ```
 
 ### Examples
@@ -59,6 +58,7 @@ ksonnet validate prod -c redis
       --context string                 The name of the kubeconfig context to use
   -V, --ext-str stringSlice            Values of external variables
       --ext-str-file stringSlice       Read external variable from a file
+  -h, --help                           help for validate
       --insecure-skip-tls-verify       If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure
   -J, --jpath stringSlice              Additional jsonnet library search path
       --kubeconfig string              Path to a kubeconfig file. Alternative to env var $KUBECONFIG.
@@ -82,5 +82,6 @@ ksonnet validate prod -c redis
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 

docs/cli-reference/ks_version.md

@@ -5,7 +5,6 @@ Print version information for this ksonnet binary
 ### Synopsis
 
 
-
 The `version` command prints out version info about the current ksonnet CLI,
 as well as for any of its helper libraries (e.g. `client-go`).
 
@@ -13,7 +12,13 @@ as well as for any of its helper libraries (e.g. `client-go`).
 
 
 ```
-ks version
+ks version [flags]
+```
+
+### Options
+
+```
+  -h, --help   help for version
 ```
 
 ### Options inherited from parent commands
@@ -23,5 +28,6 @@ ks version
 ```
 
 ### SEE ALSO
+
 * [ks](ks.md)	 - Configure your application to deploy to a Kubernetes cluster
 

vendor/github.com/spf13/cobra/.travis.yml

@@ -2,8 +2,8 @@ language: go
 
 matrix:
   include:
-    - go: 1.7.5
-    - go: 1.8.1
+    - go: 1.7.6
+    - go: 1.8.3
     - go: tip
   allow_failures:
     - go: tip

vendor/github.com/spf13/cobra/args.go

+package cobra
+
+import (
+	"fmt"
+)
+
+type PositionalArgs func(cmd *Command, args []string) error
+
+// Legacy arg validation has the following behaviour:
+// - root commands with no subcommands can take arbitrary arguments
+// - root commands with subcommands will do subcommand validity checking
+// - subcommands will always accept arbitrary arguments
+func legacyArgs(cmd *Command, args []string) error {
+	// no subcommand, always take args
+	if !cmd.HasSubCommands() {
+		return nil
+	}
+
+	// root command with subcommands, do subcommand checking.
+	if !cmd.HasParent() && len(args) > 0 {
+		return fmt.Errorf("unknown command %q for %q%s", args[0], cmd.CommandPath(), cmd.findSuggestions(args[0]))
+	}
+	return nil
+}
+
+// NoArgs returns an error if any args are included.
+func NoArgs(cmd *Command, args []string) error {
+	if len(args) > 0 {
+		return fmt.Errorf("unknown command %q for %q", args[0], cmd.CommandPath())
+	}
+	return nil
+}
+
+// OnlyValidArgs returns an error if any args are not in the list of ValidArgs.
+func OnlyValidArgs(cmd *Command, args []string) error {
+	if len(cmd.ValidArgs) > 0 {
+		for _, v := range args {
+			if !stringInSlice(v, cmd.ValidArgs) {
+				return fmt.Errorf("invalid argument %q for %q%s", v, cmd.CommandPath(), cmd.findSuggestions(args[0]))
+			}
+		}
+	}
+	return nil
+}
+
+// ArbitraryArgs never returns an error.
+func ArbitraryArgs(cmd *Command, args []string) error {
+	return nil
+}
+
+// MinimumNArgs returns an error if there is not at least N args.
+func MinimumNArgs(n int) PositionalArgs {
+	return func(cmd *Command, args []string) error {
+		if len(args) < n {
+			return fmt.Errorf("requires at least %d arg(s), only received %d", n, len(args))
+		}
+		return nil
+	}
+}
+
+// MaximumNArgs returns an error if there are more than N args.
+func MaximumNArgs(n int) PositionalArgs {
+	return func(cmd *Command, args []string) error {
+		if len(args) > n {
+			return fmt.Errorf("accepts at most %d arg(s), received %d", n, len(args))
+		}
+		return nil
+	}
+}
+
+// ExactArgs returns an error if there are not exactly n args.
+func ExactArgs(n int) PositionalArgs {
+	return func(cmd *Command, args []string) error {
+		if len(args) != n {
+			return fmt.Errorf("accepts %d arg(s), received %d", n, len(args))
+		}
+		return nil
+	}
+}
+
+// RangeArgs returns an error if the number of args is not within the expected range.
+func RangeArgs(min int, max int) PositionalArgs {
+	return func(cmd *Command, args []string) error {
+		if len(args) < min || len(args) > max {
+			return fmt.Errorf("accepts between %d and %d arg(s), received %d", min, max, len(args))
+		}
+		return nil
+	}
+}