Releases: FairwindsOps/reckoner
Releases · FairwindsOps/reckoner
v1.0.2
v1.0.1
[1.0.1]
Fixed
- Reckoner would silently fail when a --only or --heading was defined for a
chart that didn't exist in your course.
This behavior will still succeed if you provide at least one valid --heading
value. If no values are in your course then this bubbles up an error - Internal Fix: Reckoner Errors now are a single parent exception class
- Fixed hook output to user instead of hidden only in debug (#59)
- Fixed hooks to run from the same path as course.yml. This makes PWD relative
to course.yml for easier groking of paths for hook pre/post install.
v1.0.0
[1.0.0]
Fixed
version
command is fixedgenerate
command is removed (was broken for several versions)
Changes
- Adjusted schema to support
set
option for charts- This will translate all elements into
--set key=value
for the helm run - Current behavior actually does this for
values: {}
- All
values:
uses will warn that future versions will be type strong
- This will translate all elements into
- More testing for CLI contract options
Deprecation Notice
In the future, the values: {}
configuration of a chart will change the
behavior (see Issue #7). The current behavior translates any values:{}
into
--set
for the command line helm. This makes certain object types lose their
type fidelity. This means true
becomes string("true")
when pushed through
--set values=true
. To maintain the same behavior for your settings please
change values:{}
to set-values:{}
. This behavior deprecaton will start to
be enforces in later versions of Reckoner.
v0.11.1
v0.11.0
v0.10.3
v0.10.2
Fixed
- fixing error were value-strings from the course where not being set as
set-string on the command line - improved output when a desired environment variable is not set
- no longer adding the helm_args from course.yml twice
v0.10.1
v0.10.0
[0.10.0]
Major-ish refactor to class structure and testing of independent classes in code. More work will be coming to make test coverage better.
Added
- Default arguments for helm now do the right thing if using global flags for connecting to tiller (
tiller-namespace
, etc)
Fixed
- Bubbled up actual error messages from Helm commands if they have a non-zero exit code
Breaking Changes
- None expected but this is a refactor of the helm client interface
Notes
Found several bugs that are noted in code and here. Fixes will be forthcoming.
- Found that rollback functionality isn't operational
- Found that dependency_update is non-operational
- Found that kubectl context update isn't functional