65ee6a2124
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 |
||
|---|---|---|
| .. | ||
| app.go | ||
| app_test.go | ||
| ask.go | ||
| config.go | ||
| constants.go | ||
| constants_test.go | ||
| context.go | ||
| desired_state_file_loader.go | ||
| errors.go | ||
| load_opts.go | ||
| run.go | ||
| two_pass_renderer.go | ||
| two_pass_renderer_test.go | ||