1. 31 Oct, 2017 3 commits
    • Jessica Yuen's avatar
      Expand environment params.libsonnet · d55fbed6
      Jessica Yuen authored
      Expose the import path to environments/:env/params.libsonnet as an
      ExtCode so that it is made accessible to component files during
    • Jessica Yuen's avatar
      Generate environment param file · 16af8bcc
      Jessica Yuen authored
      This commit will generate the `environments/<env>/params.libsonnet` file
      on `env add <env>`.
      The purpose of this file is to allow users to define custom parameters
      on an environment-to-environment basis. It is meant to allow for
      "overrides" to component params.
    • Jessica Yuen's avatar
      Generate components/params.libsonnet file · 53af2792
      Jessica Yuen authored
      The purpose of this file is to allow re-parameterization of components
      after they are created.
      `components/params.libsonnet` is generated on `ks init`. This file will
      contain a jsonnet obj containing two objs:
      1. global: contains user-defined global parameters; accessible to all
      component and environments.
      2. components: contains component-level parameters, defined initially
      from `ks prototype use ...`
      These objs are empty by default.
  2. 26 Oct, 2017 9 commits
  3. 25 Oct, 2017 6 commits
  4. 23 Oct, 2017 1 commit
  5. 20 Oct, 2017 1 commit
    • Jessica Yuen's avatar
      Remove link to releases page · 152d34f8
      Jessica Yuen authored
      ksonnet.next isn't released yet. This message remained as a port from
      the original README file in the kubecfg project.
  6. 19 Oct, 2017 1 commit
  7. 17 Oct, 2017 6 commits
  8. 06 Oct, 2017 6 commits
    • Jessica Yuen's avatar
      Expand environment .jsonnet file · 6378e75a
      Jessica Yuen authored
      Commands that take `env` as a param currently expand all files in the
      `components` directory. This is no longer necessary with the
      introduction of `base.libsonnet` and the per-environment override
      `<env>.jsonnet` file.
      This commit will simply expand the single `<env>.jsonnet` file (which
      will implicitly expand all component files). The case of running
      `ksonnet apply default`, is equivalent to running `ksonnet apply -f
    • Jessica Yuen's avatar
      Add test for Manager.LibPaths · fdbdf59a
      Jessica Yuen authored
    • Jessica Yuen's avatar
      Generate per-environment override file · 43896a67
      Jessica Yuen authored
      This commit will generate an "<env-name>.jsonnet" file when an
      environment is created.
      For example, the default environment would have the following tree
      ├── environments
      │   ├── base.libsonnet
      │   └── default
      │       ├── .metadata
      │       │   ├── k.libsonnet
      │       │   ├── k8s.libsonnet
      │       │   └── swagger.json
      │       ├── default.jsonnet
      │       └── spec.json
      The goal of this file is to allow users to extend on base.libsonnet on a
      per-environment basis to allow for custom overrides, such as replica
    • Jessica Yuen's avatar
      Generate base.libsonnet in environments/ · 4b50beb8
      Jessica Yuen authored
      base.libsonnet is a generated file that exists at the root of the
      environments directory. This file is generated for all ksonnet projects.
      The main goal of this file is to import all components in the components
      directory, so that environments are able to easily extend / override any
      one of these components in a modular structure.
    • Jessica Yuen's avatar
      Add .metadata folder to env dir structure · f95863fc
      Jessica Yuen authored
      This change simply hides the environment metadata details that we do not
      want users directly modifying into a .metadata folder.
    • Alex Clemmer's avatar
      Merge pull request #170 from jessicayuen/default-namespace-fix · 2169ce8b
      Alex Clemmer authored
      Remove unnecessary param from defaultNamespace()
  9. 05 Oct, 2017 1 commit
    • Jessica Yuen's avatar
      Remove unnecessary param from defaultNamespace() · c95cde93
      Jessica Yuen authored
      The `clientConfig` param currently being passed is not needed, because
      it exists as a package level var in root. It also makes little sense to
      pass a custom `clientConfig` because if `overrides.Context.Namespace` is
      populated, the namespace that is returned is configured as an override
      in the package level `clientConfig` and not the `clientConfig` in the
  10. 03 Oct, 2017 4 commits
  11. 27 Sep, 2017 2 commits