1. 23 Feb, 2018 1 commit
    • Jessica Yuen's avatar
      App spec to take a single destination · 936e31ab
      Jessica Yuen authored
      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
      Signed-off-by: default avatarJessica Yuen <im.jessicayuen@gmail.com>
  2. 22 Feb, 2018 3 commits
  3. 21 Feb, 2018 2 commits
  4. 17 Feb, 2018 3 commits
  5. 08 Feb, 2018 4 commits
  6. 05 Feb, 2018 1 commit
  7. 02 Feb, 2018 1 commit
    • Jessica Yuen's avatar
      Migrate environment spec.json to the app.yaml model · 19b3b928
      Jessica Yuen authored
      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
          - namespace: foo
            server: example.com
          k8sVersion: "1.8.1"
          path: dev
          - 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: default avatarJessica Yuen <im.jessicayuen@gmail.com>
  8. 01 Feb, 2018 5 commits
  9. 31 Jan, 2018 5 commits
  10. 30 Jan, 2018 4 commits
  11. 26 Jan, 2018 3 commits
  12. 25 Jan, 2018 2 commits
  13. 24 Jan, 2018 1 commit
  14. 22 Jan, 2018 2 commits
    • Jess's avatar
      Merge pull request #288 from jessicayuen/component-rm · 4cb12c84
      Jess authored
      Add remove component functionality
    • Jessica Yuen's avatar
      Add remove component functionality · 8f26d9a4
      Jessica Yuen authored
      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: default avatarJessica Yuen <im.jessicayuen@gmail.com>
  15. 19 Jan, 2018 3 commits