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.