mirror of
https://github.com/helmfile/helmfile.git
synced 2026-10-01 13:09:51 +02:00
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
24 lines
828 B
AMPL
24 lines
828 B
AMPL
module github.com/roboll/helmfile
|
|
|
|
go 1.12
|
|
|
|
require (
|
|
github.com/Masterminds/semver v1.4.1
|
|
github.com/Masterminds/sprig v2.16.0+incompatible
|
|
github.com/aokoli/goutils v1.0.1 // indirect
|
|
github.com/google/go-cmp v0.3.0
|
|
github.com/google/uuid v0.0.0-20161128191214-064e2069ce9c // indirect
|
|
github.com/huandu/xstrings v1.0.0 // indirect
|
|
github.com/imdario/mergo v0.3.6
|
|
github.com/mattn/go-runewidth v0.0.4 // indirect
|
|
github.com/pkg/errors v0.8.1 // indirect
|
|
github.com/tatsushid/go-prettytable v0.0.0-20141013043238-ed2d14c29939
|
|
github.com/urfave/cli v0.0.0-20160620154522-6011f165dc28
|
|
go.uber.org/atomic v1.3.2 // indirect
|
|
go.uber.org/multierr v1.1.0 // indirect
|
|
go.uber.org/zap v1.8.0
|
|
golang.org/x/crypto v0.0.0-20180403160946-b2aa35443fbc // indirect
|
|
gopkg.in/yaml.v2 v2.2.1
|
|
gotest.tools v2.2.0+incompatible
|
|
)
|