Open EronWright opened 7 months ago
Note that Chart v4 has the suggested behavior; when chart dependency resolution fails, and there's a lock file, Chart v4 automatically runs helm dependency build
. The remaining work would be to backport to Release v3 and/or to implement it in Release v4.
Hello!
Issue details
Helm v3 supports the use of a lockfile (
Chart.lock
orrequirements.lock
) to reconstruct a chart's dependencies to the state specified in the lock file. Used withhelm dependency build
to not re-negotiate dependencies, ashelm dependency update
does. https://helm.sh/docs/helm/helm_dependency_build/#helm-dependency-buildPulumi should respect the lockfile when it exists. Note that Pulumi doesn't have a
--dependency-update
flag as Helm does withhelm install
; unlike Helm, Pulumi always updates the dependencies (without respecting the lockfile).Suggested Change
I would suggest that Pulumi use
helm dependency build
rather thanhelm dependency update
, which will respect the lockfile if one exists, and falls back toupdate
otherwise. Note that Helm will return an error if the lockfile is out-of-date, e.g.:Affected area/feature