Use new ksonnet lib generator

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

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

Create support for plugins in ksonnet

Set param boolean types as strings

Fixes #311

There currently exists a discrepency between the param types expected
from:
1. The parts library and in generate / prototype use
2. ks param set

ks param set will set boolean types as jsonnet boolean types, however,
prototypes will set boolean types as strings (i.e. in quotes). This
change will make it such that ks param sets boolean types as strings.
The reason we're not setting booleans in both model is because that will
require a better dependency story around ksonnet/parts first.

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

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

Fix bug with invalid base.libsonnet import path

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

There exists a bug in the reference path of base.libsonnet for nested
environment directories. We are referencing a hardcoded import
"../base.libsonnet". The works for top level environment directories but
obviously does not work for nested directories.

This commit will add the environments directory as a global lib path.

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

App spec to take a single destination

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

Currently the app.yaml spec takes a list of destinations. The change
exists to anticipate support for an environment supporting multiple
clusters or "destinations". The problem is, while the use case makes
sense for `apply`, and `delete`, it becomes ambiguous which cluster is
being referred to during commands such as `diff`. We've considered
specifying a cluster during a `diff`, however, ks currently doesn't have
a notion of a cluster identity. This change is to update the app.yaml to
take a single destination to more accurately represent the state of
things.

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

Add warning for running deprecated ks app against ks >= 0.9.0

This is a temporary piece of code that should be removed after 1.0.0.

This warning exists to tell users that are using ks < 0.9.0 with the
dated environments model (contains the 'spec.json' file), to migrate to
the newer 'app.yaml' model.

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

Pull client-go logic out of cmd/root.go and into client/ package

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

Introduce component namespaces

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

* Also setup configuration to automatically prune tests and
unused-packages

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

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

Add LibManager for managing k8s API and ksonnet-lib metadata

This change will introduce a lib package that handles the reading,
writing, and serialization of the ksonnet-lib and the kubernete's open
API files.

Prior to this change, metadata was stored in an environment's .metadata
directory. This lead to redundant files where environments share the
same kubernetes API version.

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

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

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

Migrate environment spec.json to the app.yaml model

Currently spec.json contains detail about an environment's namespace and
server. Following the proposal at
design/proposals/modular-components.md, this change will consolidate
environment specifications in the common ksonnet app.yaml file.

An environment specification for the environment "dev", may look as
follows:

environments:
  dev:
    destinations:
    - namespace: foo
      server: example.com
    k8sVersion: "1.8.1"
    path: dev
    targets:
    - db

Note: This change currently doesn't support

(1) population of the k8sVersion field. This will occur as we migrate
the environment .metadata folder.
(2) deployment to more than one destination. This will occur once ks
supports multi-cluster deployment.
(3) setting of details other than the env name in `ks env set`. Prior
to this change, users are able to namespace and server URI, however it
becomes ambiguous which namespace is being set for an environment where
there can be multiple destinations. We will encourage configuration in
app.yaml itself.
(4) targets. This will come in a later change.

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

Add interface for Environment Spec

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

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

Extract ksonnet generator

extracts ksonnet generator to a new package to make it easier to incorporate in new code

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

[docs] Clarify prototypes + add troubleshooting issue

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

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

updating 1.0 roadmap

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

use afero when possible

Use afero when possible to allow for fs flexibitily (in tests or other instances).

fixes #39

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

Proposal: Modular components and cleaner environments