App spec to take a single destination
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>
Showing
- client/client.go 4 additions, 5 deletionsclient/client.go
- cmd/root.go 2 additions, 3 deletionscmd/root.go
- integration/integration_suite_test.go 3 additions, 5 deletionsintegration/integration_suite_test.go
- metadata/app/schema.go 18 additions, 22 deletionsmetadata/app/schema.go
- metadata/app/schema_test.go 28 additions, 44 deletionsmetadata/app/schema_test.go
- metadata/environment.go 4 additions, 6 deletionsmetadata/environment.go
- metadata/environment_test.go 4 additions, 6 deletionsmetadata/environment_test.go
- pkg/kubecfg/env.go 2 additions, 4 deletionspkg/kubecfg/env.go
- testdata/testapp/app.yaml 2 additions, 2 deletionstestdata/testapp/app.yaml
Please register or sign in to comment