Forcing --reset-values in helm exec

[mumoshu]

Extracted from #60 (comment)

TL;DR; Not specifying --reset-values while calling out helm upgrade --install in the context of Helmfile seems completely wrong to me right now.

Can we just force it?

[mumoshu]

For more context on why helm retain previously set values unless you explicitly reset it with --reset-values or override with --set, see helm/helm#1569 (comment)

We actually went from your expected case to this behavior because of community demand. The rationale behind the move was: If user A does a release, and then leaves and the app breaks, user B needs to be able to re-deploy with the same set of configs (and the minimal amount of work). Going to the defaults would be a confusing experience for user B.

This doesn't apply to helmfile, by its nature, as your helmfile.yaml is version-controlled and shared safely across your team as the desired state of your system.

cc/ @sstarcher

[sstarcher]

....This explains exactly why I was noticing some values not update... I can't believe I forgot about this.

I would 100% agree with you that this should be the default. It "might" make sense in some situations to allow the user to disable the flag as the user may only want to update the chart versions, but that could be discussed as a later enhancement.

[mumoshu]

Thanks for the confirmation. Yes, I'm open to the future discussion about adding the opt-out flag.
For now, let's start by just forcing --reset-values!

[Stono]

I really need this, it's pretty critical for me to use helmfile

[mumoshu]

@Stono So am I! And here it is: #141

[mumoshu]

v0.15.0 has been released with the fix for this.

[Stono]

woo hoo \o/