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

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

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

* relocate part related code to `pkg/registry`

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

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

* component list
* env describe
* env list
* env targets
* import
* ns create
* ns list
* param list
* param set

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

New component pipeline can handle jsonnet, yaml, and json components

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

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

Parameters are the customizable fields defining ksonnet components. For
example, replica count, component name, or deployment image.

Parameters are also able to be defined separately across environments.
Meaning, this supports features to allow a "development" environment to
only run a single replication instance for it's components, whereas
allowing a "production" environment to run more replication instances to
meet heavier production load demands.

'ks param set' is defined as follows:
  'ks param set <component-name> <param-key> <param-value>'

Examples:

Updates the replica count of the 'guestbook' component to 4.
  'ks param set guestbook replicas 4'

Updates the replica count of the 'guestbook' component to 2 for the
environment 'dev'
  'ks param set guestbook replicas 2 --env=dev'

Fixes #35

Basic skeleton.  Can evaluate jsonnet and show the output as yaml or
json .. and that's about it.