1. 27 Dec, 2017 1 commit
    • Timofey Kirillov's avatar
      Show kind in resource-not-found-in-release error · 13cb8d82
      Timofey Kirillov authored
      This error occures when resource is not found in helm release:
      `Error: UPGRADE FAILED: no resource with the name "redis-cluster-sentinel" found`
      
      Changed to:
      `Error: UPGRADE FAILED: no ConfigMap with the name "redis-cluster-sentinel" found`
      
      So now that resource can easily be found in cluster.
      13cb8d82
  2. 24 Dec, 2017 1 commit
  3. 23 Dec, 2017 1 commit
  4. 22 Dec, 2017 2 commits
  5. 21 Dec, 2017 2 commits
  6. 20 Dec, 2017 2 commits
  7. 19 Dec, 2017 2 commits
  8. 18 Dec, 2017 2 commits
  9. 14 Dec, 2017 3 commits
  10. 13 Dec, 2017 4 commits
    • Julian's avatar
      feat(helm): support namespace and additional values in lint (#2972) · ca415ab8
      Julian authored
      * Add "--namespace" to helm lint
      
      Keep lint syntax as close as possible to "helm install" resp. "helm
      upgrade", so that one only needs to change the command.
      
      See #2036
      
      * Align lintCmd struct
      
      * Add "--set" and "--values" to helm lint
      
      Keep lint syntax as close as possible to "helm install" resp. "helm
      upgrade", so that one only needs to change the command.
      
      Closes #2495,#2036
      
      * Reuse strict parameter, when rendering during lint
      
      We want to see the rendering fail, if we missed a value, so we reuse
      "--strict".
      
      See #2495,#2036
      
      * Fix lint unit test
      
      See #2495,#2036
      
      * Update docs
      ca415ab8
    • Matthew Fisher's avatar
      Merge pull request #3190 from mattfarina/feat/status-json · 6707fe04
      Matthew Fisher authored
      feat(status): Optional output as JSON and YAML
      6707fe04
    • Mitchel Humpherys's avatar
      6de70254
    • Mitchel Humpherys's avatar
      feat(repo): Improve error message for missing repositories.yaml · 7417f092
      Mitchel Humpherys authored
      New users to helm don't always run `helm init` (e.g. if their cluster
      already has helm installed).  The user's initial interaction with any of
      helm's repository commands (e.g. `helm repo list`) will then be an error
      message due to a missing repositories.yaml in their local config.
      
      Give the user a little hint about how to fix the error without them having
      to hunt through the man/help pages.
      7417f092
  11. 12 Dec, 2017 4 commits
  12. 11 Dec, 2017 1 commit
  13. 06 Dec, 2017 2 commits
  14. 05 Dec, 2017 1 commit
  15. 01 Dec, 2017 5 commits
  16. 30 Nov, 2017 1 commit
  17. 29 Nov, 2017 4 commits
  18. 28 Nov, 2017 2 commits