Feature Request: How to update Helm chart dependencies when pulling it from git
complete
J
Jade Wolf
Description:
Helm chart dependencies are not supported in Git source repositories (Harness Source Repo Providers).
Motivation:
In order to use helm library, which we developed internally, as part of workflow we need to execute "helm dependescies build" which is currently not available in Harness.
How is this currently done:
Terribly wrong: we have to commit helm library tarball into our git repository as there's no other way to execute it even as shell step.
Impact:
No binaries should exist in Git VCS but using Harness in this use case is not possible otherwise. This is serious limitation for a widely adopted tool.
Solution:
Should be trivial command sitting next to existing two "fetch" and "pull" or simply a checkbox "Resolve dependencies". The first looks more consistent with what's currently implemented.
Log In
Canny AI
Merged in a post:
Helm Dependencies
G
Graceful Marmoset
Currently Harness only supports getting dependencies from a sub-path inside of the Helm Chart that is being deployed. We'd like the ability to define a path that isn't within the Chart directory or have a separate section in the Service Configuration altogether that will allow us to download the Dependencies from Git. Currently, our directory structure is something like this
charts/
subcharts/
my-sub-chart1/
my-sub-chart2/
maincharts/
my-main-chart1/
my-main-chart2/
And our dependencies list is defined like this
repository: file://../../charts/some_subchart
Because of this, when the main chart is fetched, the sub-chart dependencies aren't fetched causing dependency issues with the Deployment. Currently, it's only possible to have dependencies when the sub-charts are located in the /charts directory of a main chart i.e. charts/maincharts/my-main-chart1/charts/my-sub-chart.
We'd like the ability to be able to be able to have our directory structure and still fetch the dependencies for Deployment in Harness.
Shylaja Sundararajan
Hi Dustin
Could you help us with a rough number of Helm Chary deployments that requires this dependency configuration support
Regards
Shylaja
Rohan Gupta
complete
We have launched a feature called Service Hooks to address this use case. We have an example in our docs. Docs are published here: https://developer.harness.io/docs/continuous-delivery/deploy-srv-diff-platforms/helm/cd-helm-category/deploy-helm-charts/#service-hooks