Renovate: Helmv3 Manager should update Chart.lock

[Preisschild]

What would you like Renovate to be able to do?

The new Helm 3 Manager currently only updates the version, but doesnt update the sha256sum in the Chart.lock file thats next to Chart.yaml

Did you already have any implementation ideas?
The issue could be solved by installing Helm 3 inside the Dockerfile and add a postUpdateOption that executes helm dep up and commites those changes.

Are there any workarounds or alternative ideas you've tried to avoid needing this feature?
executing helm dep up yourself and commit those changes in the MR branch

[rarkins]

Does helm dep up only update the sha256 or does it modify more?

Have you confirmed that running the command after a Renovate update works as expected? Eg it doesn't confuse helm because we've updated the version without updating the checksum?

[Preisschild]

helm dep up also downloads the chart that is specified in depencies, but this shouldnt be an issue as that should be ignored in the .gitignore anyways.

[arbourd]

Does helm dep up only update the sha256 or does it modify more?

Updates the Chart.lock and downloads the dependencies as tarballs, as @Preisschild mentioned. ~In order for this to work, the Renovate runner would need to add the Helm chart repositories beforehand.~

You can't update the Chart.yaml without updating the Chart.lock in v3. You will get errors when you try to install the chart.

An updated Chart.lock alongside the Chart.yaml looks like:

[rarkins]

In order for this to work, the Renovate runner would need to add the Helm chart repositories beforehand.

Can you help me understand this?

[arbourd]

@rarkins Actually, I'm wrong! 😅 Previously, you would need to helm repo add <repository-name> <repository-url> before attempting to build/update dependencies.

It appears that helm dependency update no longer requires repositories to be added ahead of time. helm dependency build does require repositories to be added though.

I do not think Renovate would need to call build -- update is probably what we need.

[allymparker]

Any updates on this? Anything I can do to help?

[rarkins]

@allymparker assigned! Happy to review any PR

[allymparker]

I'm happy to submit a PR, but I'm a bit lost as to where to start!

[mikebryant]

@allymparker some info for you:
This sort of update is done by the updateArtifacts function, part of the ManagerApi interface.

There's existing examples in lib/manager/*/artifacts.ts, e.g. https://github.com/renovatebot/renovate/blob/master/lib/manager/cargo/artifacts.ts

I think what's needed is to create lib/manager/helmv3/artifacts.ts, and add import { updateArtifacts } from './artifacts'; to lib/manager/helmv3/index.ts. (And add tests)

For the docker image, the helm dependency would need to be added in https://github.com/renovatebot/docker-renovate-full/blob/master/Dockerfile

[viceice]

For the app we will need a renovate/helm docker image, because the app uses binarySource=docker!

[renovate-release]

:tada: This issue has been resolved in version 23.68.0 :tada:

The release is available on:

• GitHub release
• 23.68.0

Your semantic-release bot :package::rocket: