Skip to content
Snippets Groups Projects
  1. Jan 25, 2018
  2. Jan 22, 2018
    • 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>
      8f26d9a4
  3. Jan 11, 2018
  4. Jan 08, 2018
  5. Jan 05, 2018
  6. Dec 20, 2017
  7. Dec 15, 2017
    • Jessica Yuen's avatar
      Implement command `ks registry add` · 4e0b163e
      Jessica Yuen authored
      
      Currently users are unable to add their own registries through the CLI.
      This limits them to a small subset of prototypes found in the default
      incubator registry.
      
      This commit will add the command `ks registry add`, that allows users to
      add registries supporting the `github` protocol.
      
      It will be of the form `ks registry add <registry-name> <registry-uri>
      [--version]`. If a version is not specified, `latest` will be used.
      
      Signed-off-by: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      4e0b163e
  8. Dec 11, 2017
  9. Dec 04, 2017
  10. Dec 03, 2017
  11. Dec 01, 2017
  12. Nov 30, 2017
  13. Nov 29, 2017
    • Jessica Yao's avatar
      fix cli docs for ks-prototype · 7d9f57ae
      Jessica Yao authored
      
      Signed-off-by: default avatarJessica Yao <jessica@heptio.com>
      7d9f57ae
    • Alex Clemmer's avatar
      :muscle: Make env-name a required param in "env commands" · 4923a3f5
      Alex Clemmer authored
      
      Fixes #100.
      
      This commit will transition the ksonnet CLI away from accepting either a
      list of files or an environment (or both). A detailed explanation
      follows.
      
      Historically, the ksonnet CLI has had several "environment commands".
      These commands (e.g., `apply`, `diff`, `delete`, `show`, etc.) all took
      one of the following:
      
        1. An environment name. For example, `apply us-west/dev` will `apply`
           everything in the `components/` directory to the cluster denoted by
           `us-west/dev`.
        2. A set of files. For example, `apply -f foo.jsonnet -f bar.jsonnet`
           would apply those two specific Jsonnet files to the server
           specified by the current context in $KUBECONFIG.
        3. Both an environment name and a set of files. For example,
           `apply us-west/dev -f foo.jsonnet -f bar.jsonnet` would `apply`
           those two files to the cluster denoted by the `us-west/dev`
           environment.
      
      This "duality" remained in place primarily because it was important for
      the ksonnet CLI to maintain functional compatibility (though not strict
      CLI-level app compatibility) with the kubecfg tool.
      
      Some time ago the ksonnet CLI was forked from the kubecfg CLI, but it is
      only in this commit that we abandon this duality. Specifically, this
      commit will _require_ the environment name for all commands. For
      example, the form of `apply` will now be:
      `apply <env-name> [-f <file>]`.
      
      There are main parts to this:
      
        1. Refactoring core abstractions that supports this "duality".
           Specifically, removing the `cmd.envSpec` type and several
           functions, such as `cmd.parseEnvCmd`.
        2. Updating the tests to reflect this new directory structure.
      
      Signed-off-by: default avatarJessica Yuen <im.jessicayuen@gmail.com>
      4923a3f5
    • bryanl's avatar
      Add support for custom directory location for ks app · a02fffb3
      bryanl authored
      
      * If custom dir is relative, it is created relative to CWD
      * if custom dir is absolute, it is created at the specificed location
      * if custom dir is not specified, a directory created at CWD/app-name is created
      
      Signed-off-by: default avatarbryanl <bryanliles@gmail.com>
      a02fffb3
  14. Nov 27, 2017
  15. Nov 26, 2017
  16. Nov 22, 2017
  17. Nov 21, 2017
    • Jessica Yuen's avatar
      Improve ks init help message · 786a63b6
      Jessica Yuen authored
      Specifically,
      
      1. Place more emphasize on project initialization based on context
      2. Place ksonnet-lib details into footer.
      3. Order examples based on most common use cases.
      4. Suggest to visit ks generate
      786a63b6
  18. Nov 20, 2017