Closed j-m-harris closed 1 year ago
What happened?
While deploying a dependency with a custom chart name an error is reported for helm dependency update, though the helm upgrade succeeds.
helm dependency update
helm upgrade
myapp deploy:myapp error running helm dependency update: error executing 'helm dependency update --kube-context minikube': Error: Chart.yaml file is missing myapp deploy:myapp Deployed helm chart (Release revision: 1)
What did you expect to happen instead?
helm dependency update should use the same custom chart name as helm upgrade to avoid an error.
How can we reproduce the bug?
Using devspace 5 config file schema with devspace 6.2.3.
Chart name is defined in a dependency, although I don't know if that is relevant to this bug.
main devspace.yaml:
version: v1beta11 dependencies: - name: myapp source: git: git@gitlab:myapp.git
myapp devspace.yaml specifies a custom helm chart name:
version: v1beta11 deployments: - name: myapp helm: chart: name: ./chart
Invoking helm directly in the devspace dependency checkouts:
cd ~/.devspace/dependencies/git-gitlab-myapp-master helm dependency update --kube-context minikube # fails helm dependency update ./chart --kube-context minikube # works
Local Environment:
Thanks for the quick fix!
What happened?
While deploying a dependency with a custom chart name an error is reported for
helm dependency update
, though thehelm upgrade
succeeds.What did you expect to happen instead?
helm dependency update
should use the same custom chart name ashelm upgrade
to avoid an error.How can we reproduce the bug?
Using devspace 5 config file schema with devspace 6.2.3.
Chart name is defined in a dependency, although I don't know if that is relevant to this bug.
main devspace.yaml:
myapp devspace.yaml specifies a custom helm chart name:
Invoking helm directly in the devspace dependency checkouts:
Local Environment: