[docs] Remove (now optional) `--name` syntax from `ks generate` commands

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Revert "Update default version in Makefile to v0.7.0"

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Implement github token to work around rate limits

Signed-off-by: Joe Beda <joe.github@bedafamily.com>

Update default version in Makefile to v0.7.0

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

[docs] Relax 1.8 req

Signed-off-by: Jessica Yao <jessica@heptio.com>

[docs] Formalize container image names

Vendor ksonnet-lib/ksonnet-gen | Log warning on k8s v1.8.x

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

[doc] Updates/polish

Signed-off-by: Jessica Yao <jessica@heptio.com>

Parse short description for prototypes

Signed-off-by: Jessica Yao <jessica@heptio.com>

[docs] Clean up all CLI reference help/docs

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Signed-off-by: Jessica Yao <jessica@heptio.com>

Update apply CLI docs

Primarly,

1. Emphasize on the new '-c' flag, removing '-f'.
2. Adding related commands
3. Clarifying the use cases for apply

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Rewrite integration tests to support ksonnet.next application structure

[docs] Fix CLI reference for `ks-prototype`

Signed-off-by: Jessica Yao <jessica@heptio.com>

ksonnet.next is centered around the application directory structure
generated during init, however the integration tests are still tightly
tied to the model from kubecfg, where the '-f' flag was the standard and
environments were not introduced.

This commit will add test fixtures to mock a ksonnet application
structure, and rewrite the existing apply and delete tests to support
this new model.

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Currently, namespace and server is being overwritten by the environment
despite the user explicitly passing in the `--namespace` flag.

Ex: during `ks apply dev --namespace=ns2`, `ns2` should take preference
to the namespace specified by the dev environment.

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>

Fixes #100.

This commit will transition the ksonnet CLI away from accepting either a
list of files or an environment (or both). A detailed explanation
follows.

Historically, the ksonnet CLI has had several "environment commands".
These commands (e.g., `apply`, `diff`, `delete`, `show`, etc.) all took
one of the following:

  1. An environment name. For example, `apply us-west/dev` will `apply`
     everything in the `components/` directory to the cluster denoted by
     `us-west/dev`.
  2. A set of files. For example, `apply -f foo.jsonnet -f bar.jsonnet`
     would apply those two specific Jsonnet files to the server
     specified by the current context in $KUBECONFIG.
  3. Both an environment name and a set of files. For example,
     `apply us-west/dev -f foo.jsonnet -f bar.jsonnet` would `apply`
     those two files to the cluster denoted by the `us-west/dev`
     environment.

This "duality" remained in place primarily because it was important for
the ksonnet CLI to maintain functional compatibility (though not strict
CLI-level app compatibility) with the kubecfg tool.

Some time ago the ksonnet CLI was forked from the kubecfg CLI, but it is
only in this commit that we abandon this duality. Specifically, this
commit will _require_ the environment name for all commands. For
example, the form of `apply` will now be:
`apply <env-name> [-f <file>]`.

There are main parts to this:

  1. Refactoring core abstractions that supports this "duality".
     Specifically, removing the `cmd.envSpec` type and several
     functions, such as `cmd.parseEnvCmd`.
  2. Updating the tests to reflect this new directory structure.

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.com>