1. 24 Sep, 2019 1 commit
  2. 23 Sep, 2019 1 commit
  3. 19 Sep, 2019 1 commit
  4. 18 Sep, 2019 1 commit
    • Matt Farina's avatar
      Updating to newer versions of dependencies · aa4dae05
      Matt Farina authored
      * This was initiated by new versions from Masterminds
      * Linting was set to check for the same chart version as the other
        checks of this were. >0.0.0-0. The -0 is important to pull in
        prereleases. The latest version of semver Validate now finds
        errors here properly where some were missed before
      * 0.0.0 is a valid semantic version. Instead of expecting it to be
        invalid in the tests to check validation now using an invalid
        semantic version
      Signed-off-by: 's avatarMatt Farina <matt@mattfarina.com>
      aa4dae05
  5. 16 Sep, 2019 1 commit
  6. 11 Sep, 2019 2 commits
  7. 10 Sep, 2019 1 commit
  8. 09 Sep, 2019 1 commit
  9. 05 Sep, 2019 2 commits
  10. 03 Sep, 2019 1 commit
  11. 02 Sep, 2019 1 commit
  12. 30 Aug, 2019 3 commits
  13. 26 Aug, 2019 2 commits
  14. 23 Aug, 2019 3 commits
  15. 20 Aug, 2019 1 commit
  16. 19 Aug, 2019 1 commit
  17. 14 Aug, 2019 1 commit
  18. 13 Aug, 2019 2 commits
  19. 10 Aug, 2019 2 commits
  20. 09 Aug, 2019 2 commits
  21. 07 Aug, 2019 3 commits
  22. 06 Aug, 2019 3 commits
  23. 05 Aug, 2019 1 commit
  24. 03 Aug, 2019 1 commit
  25. 02 Aug, 2019 2 commits
    • Matt Farina's avatar
      Merge pull request #6152 from AllenZMC/patch-1 · fbcc5dd8
      Matt Farina authored
      fix word 'efault' to 'default'
      fbcc5dd8
    • Kevin Lau's avatar
      Clarify operator docs wording · bb69a1ed
      Kevin Lau authored
      The original is explaining the negation, when the body would not be
      included. Which would happen in the complement of the if expression,
      ie. flipped by De Morgan's law's:
      
      ```
      not (or .Values.anUnsetVariable (not .Values.aSetVariable))
      ==
      and (not .Values.anUnsetVariable) .Values.aSetVariable
      ```
      
      > unset variables evaluate to false
      
      is equivalent to `not .Values.anUnsetVariable`.
      
      > and
      
      is equivalent to `and`.
      
      > .Values.setVariable was negated with the not function
      
      doesn't seem to match `.Values.aSetVariable`.
      To me, that would be `not .Values.aSetVariable` instead.
      
      Anyway, explaining the `if` expression as-is and not the negation is
      clearer and parallels the first `if` operator.
      Signed-off-by: 's avatarKevin Lau <kelau1993@gmail.com>
      bb69a1ed