[Feature Request] helm package should have --version flag

[jchauncey]

We all know that the version of a package is derived from the Chart.yaml. However, if you are wanting to deliver a new chart artifact for each commit pushed to master changing that file is rather cumbersome (modifying a file in CI is dangerous and having to change that file for each commit seems inefficient).

Instead, it would be very useful to have a --version flag which would be part of the helm package command. This would allow us to override the value in Chart.yaml within a CI environment without mucking up the workspace.

[technosophos]

@jchauncey Just to make sure I am reading this right, you'd want that change to be written to disk, too, right?

In other words, I would be able to do this:

$ grep version Chart.yaml
version: 1.2.3
$ helm package --version 2.3.4 .
$ grep version Chart.yaml
version: 2.3.4

Does that look correct?

[jchauncey]

Yup that's awesome

…

On Dec 15, 2016 5:07 PM, "Matt Butcher" ***@***.***> wrote: @jchauncey <https://github.com/jchauncey> Just to make sure I am reading this right, you'd want that change to be written to disk, too, right? In other words, I would be able to do this: $ grep version Chart.yamlversion: 1.2.3 $ helm package --version 2.3.4 . $ grep version Chart.yamlversion: 2.3.4 Does that look correct? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1480 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAaRGHN1RTewXLzIREuOgtgQNyaMdmAYks5rIbodgaJpZM4KlTJz> .

[technosophos]

After some debate, I think the current feature will go in with this functionality:

For some package foo, helm package --version 1.2.3 foo will...

• Generate a package named foo-1.2.3.tgz
• Set version: 1.2.3 INSIDE of foo-1.2.3
• Leave the outside foo/Chart.yaml alone

This will prevent CI/CD systems (the envisioned customer of this feature) from choking on a dirty repo after a package command is run.