Hello,
Currently I'm trying to package my chart in Azure Devops using the Helm task, first I'm installing version 3.0.1 and it completes fine, but when I run 'helm package' I get the following error:
/opt/hostedtoolcache/helm/3.0.1/x64/linux-amd64/helm package --save --destination home/vsts/work/1/a/k8s/helm --values /home/vsts/work/1/s/Api-Search-Upload/build/azure-devops/values.yaml /home/vsts/work/1/s/stin-pipelines/deploy/k8s/helm/stin-microservices
Error: unknown flag: --save
##[error]Error: unknown flag: --save
This is blocking our releases, so please I hope you guys can help us.
Thanks in advance.
Regards.
It looks like you've encountered an issue with the product itself, rather than an issue with the documentation. To make sure it gets in front of the right people, please submit your bug here.
Meanwhile, you may find answers here:
I am closing this issue now. You are welcome to @ mention me for any followup.
We hope to hear from you again.
Hey @Cutux,
I had the same issue using the HelmDeploy@0 task in a YAML pipeline. The issue appears to be that the 'save' option is set to 'true' by default, but this can be suppressed by setting it to false in the YAML, e.g. --
- task: HelmDeploy@0
displayName: Helm package
inputs:
command: package
save: false
chartPath: $(CHART_DIRECTORY)
destination: $(Build.ArtifactStagingDirectory)
arguments: --app-version $(Build.BuildNumber)
You may have figured this since, but posting in case anyone else hits this issue as well.
For reference --
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops#package-command
Happy Helming!
@Cutux -- Cutu, thank you for your feedback.
@rootd00d -- Casey, thank you for finding a solution.
@azooinmyluggage -- Atul, please look into this issue.
This issue hasn't been updated in more than 180 days, so we've closed it. If you feel the issue is still relevant and needs fixed, please reopen it and we'll take another look. We appreciate your feedback and apologize for any inconvenience.
Most helpful comment
Hey @Cutux,
I had the same issue using the HelmDeploy@0 task in a YAML pipeline. The issue appears to be that the 'save' option is set to 'true' by default, but this can be suppressed by setting it to false in the YAML, e.g. --
You may have figured this since, but posting in case anyone else hits this issue as well.
For reference --
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops#package-command
Happy Helming!