v4.0.0

Changelog

5e34ec0 Enable chart level Namespace Manager (#207)
c9b6627 Add Helm Template (#208)
0ab4720 MAJOR (potentially breaking) Add --run-all. Make either run-all or only required. (#210)
5917d0d Adding get-manifests command (#212)
3360a98 Fixing template and get-manifests (#214)
c608577 Bump pytest from 5.4.3 to 6.0.1 (#216)
e590fa6 Update helm to 3.3.0 for testing and validation (#218)

v3.2.2

Changelog

b7fa057 skip tests from coverage (#192)
607dfd8 Update supported helm versions (#191)
9b6e668 Add reset() classmethod to Config. (#188)
e7cd216 Use unittest.mock (#193)
02bfa8e Test repository (#194)
f59b563 Update README.md (#198)
ba39ec1 Bump click from 7.1.1 to 7.1.2 (#199)
382ce17 Fix slack link (#200)
b8f342f Bump pytest from 5.4.1 to 5.4.2 (#201)
be34144 Bump pytest from 5.4.2 to 5.4.3 (#202)
40c1fe7 Make NamespaceManager respect --dryrun (#204)
fdc27cd Make more verbose/helpful output for --log-level=DEBUG. (#206)

v3.2.1

Changelog

010699c Update README.md (#181)
474b49e Bump click from 7.0 to 7.1.1 (#182)
8e2167b Bump kubernetes from 10.0.1 to 11.0.0 (#184)
1e307b2 Bump pytest from 5.3.5 to 5.4.0 (#183)
0e73704 Bump pytest from 5.4.0 to 5.4.1 (#185)
fee97bb Don't try to add repos without a URL (#187)
dcaafa6 Pin chart repo version in e2e test (#189)

v3.2.0

Changelog

4401e80 functional namespace management work with schema validation (#177)
545250b Adding Course pre and post install hooks (#178)

v3.1.0

Changelog

ff79459 Update HELM3_BLOCKERS.md (#166)
5d898cb Bump pytest from 5.3.2 to 5.3.3 (#167)
52bb76a Bump pytest from 5.3.3 to 5.3.4 (#169)
03b367c upgrading helm3 support to official (#171)
02c29ba Bump pytest from 5.3.4 to 5.3.5 (#172)
7bffa44 Fixes #173. Regex the comments out before interpolating env vars. (#174)
79e3fc7 Updating kubectl version to match kind cluster version. (#175)

v3.0.0

Changes

• Official Helm3 support!
• Reckoner will detect which version of the helm binary is active use it
• Will create namespaces that do not already exist as that functionality was removed in Helm 3

v2.2.0

v2.2.0

Changes

• Added a warning message when using helm3: NOTE HELM3 IS NOT YET SUPPORTED! Use at your own peril!
• Added better logging for helm errors (into debug output)
• Added better handling of uninitialized helm (client side)
• Fixed issues where helm would try to interpolate variables in comments provided in values: {} section of a chart definition
• Added better logging for debug when unexpected errors happen in python
• Added better logging output for debugging yaml parse issues
• Fixed repository git support for defining git chart endpoints at the top level and chart level

v2.1.1

v2.1.1

Fixes

• Bugfix when using values files that exist in the same path as the course file. #145

v2.1.0

v2.1.0

• Added Helm 3 detection

Breaking Changes

• Added end-to-end test for values files in sub-folders
• Schema Validation
  • We are introducing schema validation on the course.yml. This will exit hard if your course.yml has indentation errors or other issues that don't conform to the course.yml expected schema. The schema can be found at here.
  • Reckoner now blocks on YAML duplicate keys. If your yaml has duplicate keys in any section of the yaml, the course will fail to load and no actions will be performed. There is no way to allow duplicate keys in course.yml anymore to avoid inconsistent behavior or unexpected course runs.
  • More details on the implications of schema validations can be found here: docs/changelog_details/schema_validation.md.
  • As a part of defining a strict schema for course YAMLs, you will need to house any "reuable" YAML blocks in the top-level-key of _references: {}.

Fixes

• Fixed the references for values to be relative: files: [] now are referenced relative to the course yaml you're running. Also added end-to-end test for values files in subfolders.

v2.0.0

v2.0.0 🎉 🎊

Important Changes

The behavior of values: {} in the chart section of your course file has change! It was previously setting all the key/values as --set and now these are translated into native yaml, thus keeping value type consistent. Prior to 2.0.0 floats would be set as strings, double-quoted "true"/"false" would convert to bool values instead of strings, etc.

If you are unsure how this change might affect your course files, please change values: {...} to be set-values: {...} and you should see a consistent behavior.

Breaking Changes

• Changes to values: {} behavior:
  The chart: {values: {}} config block and chart: {set-values:{}} config block now have different behavior. set-values: {} always gets translated into helm arguments as --set key=value. The values: {} now gets applied to helm arguments as -f temporary_values_name.yml. The values: {} config block is now fully consistent with intended types and would behave as though you are using a -f my_values.yml in your helm command. Prior to this change you would see inconsistent type casting for float, bool and integer config settings. For more information on the behavior differences between values, set-values, and values-strings you can look at our end to end testing test course.yml.
• BUG FIX: Using "null", null, "Null", and "NULL" as values in set-values: {} will be interpreted as null (void of value) in the --set value. Previously, if you set null as the yaml value, you would get --set key=None due to python interpreting the value as None and thus would show up as {"key": "None"} in the helm values. This fix more closely aligns with expected behavior in helm.