KUOKA Yusuke 65ee6a2124 fix: "cannot unmarshal !!str <no value> into bool" errors in state templates (#645) ...

Seems like we are affected by https://github.com/golang/go/issues/24963. That is, even though we internally use the template option `missingkey=zero`, in some cases it still prints `<no value>` instead of zero values, which has been confusing the state yaml parsing.

This fixes the issue by naively replacing all the remaining occurrences of `<no value>` in the rendered text, while printing debug logs to ease debugging in the future when there is unexpected side-effects introduced by this native method.

Fixes #553

2019-06-04 13:23:38 +09:00

..

app_test.go

fix: "cannot unmarshal !!str <no value> into bool" errors in state templates (#645)

2019-06-04 13:23:38 +09:00

app.go

feat: override state(former "enviroment") values via command-line args (#644)

2019-06-04 11:03:01 +09:00

ask.go

feat: helmfile as a go library (#639)

2019-06-04 09:12:00 +09:00

config.go

feat: override state(former "enviroment") values via command-line args (#644)

2019-06-04 11:03:01 +09:00

constants_test.go

Various U/X improvements for helmfile apply (#586)

2019-05-12 16:26:11 +09:00

constants.go

feat: "bases" for easier layerina

2019-05-13 21:48:00 +09:00

context.go

chore: tidy up pkgs (#636)

2019-06-01 13:36:05 +09:00

desired_state_file_loader.go

feat: override state(former "enviroment") values via command-line args (#644)

2019-06-04 11:03:01 +09:00

errors.go

feat: Opt-out dep-builds and repo-updates (#463)

2019-02-04 12:07:25 +09:00

load_opts.go

feat: override state(former "enviroment") values via command-line args (#644)

2019-06-04 11:03:01 +09:00

run.go

feat: helmfile as a go library (#639)

2019-06-04 09:12:00 +09:00

two_pass_renderer_test.go

chore: tidy up pkgs (#636)

2019-06-01 13:36:05 +09:00

two_pass_renderer.go

fix: "cannot unmarshal !!str <no value> into bool" errors in state templates (#645)

2019-06-04 13:23:38 +09:00