You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you want to install or upgrade or template a chart and do not supply a version to use in the ChartSpec, a default version of >0.0.0-0 is set. This is the equivalent of using the helm install/upgrade/template command in the binary while also setting the --devel flag. This behavior can be dangerous if you're relying on the default being the latest stable version and not a prerelease version.
I propose the version just be left unset if not supplied. Leaving the version unset will skip prerelease versions as a viable candidate for the install/upgrade/template. Alternatively, adding a field in the ChartSpec that allows you to specify you would like to consider development versions of the chart instead of making that assumption could be an option.
Currently, if you want to install or upgrade or template a chart and do not supply a version to use in the ChartSpec, a default version of
>0.0.0-0
is set. This is the equivalent of using the helm install/upgrade/template command in the binary while also setting the--devel
flag. This behavior can be dangerous if you're relying on the default being the latest stable version and not a prerelease version.I propose the version just be left unset if not supplied. Leaving the version unset will skip prerelease versions as a viable candidate for the install/upgrade/template. Alternatively, adding a field in the ChartSpec that allows you to specify you would like to consider development versions of the chart instead of making that assumption could be an option.
https://github.com/mittwald/go-helm-client/blob/master/client.go#L300-L302
https://github.com/mittwald/go-helm-client/blob/master/client.go#L358-L360
https://github.com/mittwald/go-helm-client/blob/master/client.go#L490-L492
The text was updated successfully, but these errors were encountered: