Skip to content
Snippets Groups Projects
  1. Feb 26, 2018
    • Jessica Yuen's avatar
      Set param boolean types as strings · daf10a0a
      Jessica Yuen authored
      
      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: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      daf10a0a
    • Jess's avatar
      Merge pull request #329 from jessicayuen/base-import-fix · 6edb7b93
      Jess authored
      Fix bug with invalid base.libsonnet import path
  2. Feb 23, 2018
  3. Feb 22, 2018
  4. Feb 21, 2018
  5. Feb 17, 2018
  6. Feb 08, 2018
  7. Feb 05, 2018
  8. Feb 02, 2018
    • 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. ...
      19b3b928
  9. Feb 01, 2018
  10. Jan 31, 2018
  11. Jan 30, 2018
  12. Jan 26, 2018
  13. Jan 25, 2018
  14. Jan 24, 2018