Introduce `ks component rm <component>`. This functionality will:

1. Delete the component file from components/. This is determined by the
component file name. If there exists two files with the same name but
different file  extensions, we will error out.

2. Remove component references. This currently implies removing all
component referenes in the component/params.libsonnet file and the
environment-specific params.libsonnet files.

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

Using `Version()` as a string leaves a preprocessed version tag in the
ksonnet version. Construct a new version using the `Major` and `Minor`
fields. Adds short SHA1 from k8s.io/apimachinery as well. SHA1 is pulled
from `dep status`.

Re: #250

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

Partially implements the proposal
[here](https://github.com/ksonnet/ksonnet/blob/master/design/proposals/explicit-environment-metadata.md

)

Fixes #222

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

This adds a high level 'component' command and a 'component list'
command. 'component list' will pretty print all the components in
ksonnet application directory.

To accomplish this, an API is added to the metadata manager that returns
all components. Components are the individual files in /components, with
the path extension trimmed.

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

This adds a high level 'component' command and a 'component list'
command. 'component list' will pretty print all the components in
ksonnet application directory.

To accomplish this, an API is added to the metadata manager that returns
all components. Components are the individual files in /components, with
the path extension trimmed.

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

Signed-off-by: Levi Blackstone <levi.blackstone@rackspace.com>

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

Currently users are unable to add their own registries through the CLI.
This limits them to a small subset of prototypes found in the default
incubator registry.

This commit will add the command `ks registry add`, that allows users to
add registries supporting the `github` protocol.

It will be of the form `ks registry add <registry-name> <registry-uri>
[--version]`. If a version is not specified, `latest` will be used.

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

Currently, if we run `param set guestbook-ui foo-bar x`,

The jsonnet snippet will write: `foo-bar: "x"`.

However, this is incorrect jsonnet syntax. This commit will fix this
issue, to instead write `"foo-bar": "x"`.

Also updates the `Get...` Param functions to return non-quoted
identifiers for prettier display.

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

Currently the package name is listed before the registry name in `pkg
list`. This is inconsistent with the order of `pkg install` which is of
the format `<registry>/<package>`. This change will display the registry
name before the package name in `pkg list`.

Signed-off-by: Jessica Yuen <im.jessicayuen@gmail.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>

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

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

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>

Signed-off-by: Jessica Yao <jessica@heptio.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>

* If custom dir is relative, it is created relative to CWD
* if custom dir is absolute, it is created at the specificed location
* if custom dir is not specified, a directory created at CWD/app-name is created

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

There is a bug where the `default` environment was not using the
`--namespace` flag, even when set.

This is due to a path of execution error where `ns` is overriden during
`resolveContext`, so it will never be empty -- resulting in a check
failure in line 345.

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

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

In general, prototypes have a name param. To reduce duplication, use the component name for the name param if the name parameter is omitted. This will turn :

```
ks prototype use deployed-service guestbook-ui \
--name guestbook-ui \
--image alpinejay/dns-single-redis-guestbook:1.0 \
--type LoadBalancer
```

into

```
ks prototype use deployed-service guestbook-ui \
--image alpinejay/dns-single-redis-guestbook:1.0 \
--type LoadBalancer
```

as the `--name` parameter will be inferred. If the operator wishes the name to be different, they can supply the name parameter:

```
ks prototype use deployed-service guestbook-ui \
--name fancy-stuff \
--image alpinejay/dns-single-redis-guestbook:1.0 \
--type LoadBalancer
```

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

If the namespace is not provided in the target kubeconfig context, use
'default'.

Also squashes a bug where the namespace, server flags may have been
ignored during init.

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

Currently, if a version is not provided to the following `pkg install`
command

`../ks pkg install incubator/redis`

, the following error will occur:

`ERROR GET
https://api.github.com/repos/ksonnet/parts/commits/incubator/redis

: 404
Not Found []`

This commit will pull in the latest package from master where the
version is not specified.

Also set the default repository ref to 'master' instead of 'test-reg'.

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

Currently, commands such as `ks env non-existent-subcommand` will output
an error `Command 'env' requires a subcommand`.

This is not helpful since the user may assume there is the subcommand
'non-existent-subcommand'. This commit will clarify the error messages
in this scenario.

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

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

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

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

Output usage and return when no command args are provided for `ks diff`.

- Add message:  Creating a new app 'foo' at path '/path/to/foo'
- On success, add message:  ksonnet app successfully created! Next, try
  creating a component with `ks generate`
- On failure, provide suggestions for the user.
- Make note that the context is retrieved from the kubeconfig file at
  the environment variable $KUBECONFIG

Specifically,

1. Place more emphasize on project initialization based on context
2. Place ksonnet-lib details into footer.
3. Order examples based on most common use cases.
4. Suggest to visit ks generate

In line 161 of `root.go`, we're failing to check whether a cluster in
the $KUBECONFIG clusters array exists before using it. This will cause a
`nil` dereference error.

Update is a deprecated command that was ported over from kubecfg. Since
ksonnet has not had any releases yet, it makes little sense to keep the
command.