1. 20 Jun, 2018 1 commit
  2. 19 Jun, 2018 2 commits
  3. 12 Jun, 2018 1 commit
  4. 07 Jun, 2018 1 commit
  5. 25 May, 2018 1 commit
  6. 07 May, 2018 1 commit
  7. 20 Apr, 2018 1 commit
  8. 04 Apr, 2018 1 commit
    • bryanl's avatar
      Support env param globals · dc80ac49
      bryanl authored
      
      
      * Adds env param globals. These can be used to attach metadata labels to
      every component in an environment.
      * Print more debugging info for jsonnet vm invocations
      
      Fixes #378
      Signed-off-by: default avatarbryanl <bryanliles@gmail.com>
      dc80ac49
  9. 26 Mar, 2018 1 commit
  10. 25 Mar, 2018 1 commit
  11. 22 Mar, 2018 1 commit
  12. 05 Mar, 2018 1 commit
  13. 23 Feb, 2018 2 commits
  14. 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
      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: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      19b3b928
  15. 01 Feb, 2018 1 commit
  16. 17 Jan, 2018 1 commit
    • Alex Clemmer's avatar
      Validate app, parts, and registry schemas on deserialization · d6acd622
      Alex Clemmer authored
      
      
      Dependencies in a ksonnet application are installed from collections of
      packages called registries. In order to be precise about which packages
      an app depends on, and where they are from, we have an API that
      specifies each of these nouns.
      
      Unfortunately, we never hooked up code to verify the versions of these
      specifications as we deserialize them.
      
      This commit will correct that.
      Signed-off-by: default avatarAlex Clemmer <clemmer.alexander@gmail.com>
      d6acd622
  17. 08 Nov, 2017 1 commit
    • Alex Clemmer's avatar
      De/serialize specification objects with YAML · 56befd0f
      Alex Clemmer authored
      Fixes #48.
      
      Currently the structs `app.Spec`, `registry.Spec`, and `parts.Spec` are
      all serialized and deserialized using JSON instead of YAML.
      
      This commit will resolve this issue.
      56befd0f
  18. 07 Nov, 2017 1 commit
  19. 06 Nov, 2017 2 commits