New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm 3 changed release name parameter of helm template
#6019
Comments
@AndiDog First off, I think it's pretty fine for it to be incompatible considering the version change is a major version change v2 -> v3 About the order being mistaken, for me it doesn't sound like a solid reason. And even if it's considered as a solid reason, there will be some set of people saying otherwise - to use arguments instead of flags. The helm maintainers cannot satisfy everyone with both the features. I think users need to understand their opinions. Apart from this, some things to notice or think about:
And for me personally, it felt weird to have the release name as a flag rather than an argument. |
The release name was made mandatory as part of Helm 3. Helm will not auto-generate a name for you unless you use the So, to replicate the same behaviour, use |
--generate-name doesn't work even for helm 3. I've spent 2 hours trying to install a package. Still can't do it. I've never seen such a poorly executed CLI tool in my life. It was written by a sadist. |
@ronenmagid You could use the There is also a section on changes from Helm 2: https://helm.sh/docs/faq/#changes-since-helm-2 If you any ideas for improving this then raise an issue with your suggestions. You can work on the PR as well if you like. Hope this helps. |
Helm 2:
Helm v3.0.0-alpha.1:
This makes usage incompatible:
and having two positional (= unnamed) arguments is not a good idea in general since the order can be mistaken. I recommend reintroducing
{-n,--name}
.The text was updated successfully, but these errors were encountered: