Support helmfile helm-charts from private repositories

[mashiofu-cafex]

Tell us more.

I am looking to utilize renovate to update my helmfile helm-chart versions as new versions are released. The feature works fine for normal helmfile.yaml and repositories.yaml config, grafana example:

helmfile.yaml:

- name: grafana
  namespace: monitoring
  chart: grafana/grafana
  version: 8.5.1
  installed: true
  values:
    - grafana-values.yaml.gotmpl
    - grafana-values.yaml

repositories.yaml

repositories:
- name: grafana
  url: https://grafana.github.io/helm-charts

---

This config give me a successful run in which the renovate logs displays as follows:

{
                 "depName": "grafana",
                 "currentValue": "8.5.1",
                 "registryUrls": ["https://grafana.github.io/helm-charts"],
                 "updates": [
                   {
                     "bucket": "non-major",
                     "newVersion": "8.5.2",
                     "newValue": "8.5.2",
                     "newDigest": "20e837fc6a1e22da2ead492bb266448b30f4d12b5396355411bc8978f086a5dd",
                     "releaseTimestamp": "2024-10-02T07:45:48.603Z",
                     "newMajor": 8,
                     "newMinor": 5,
                     "newPatch": 2,
                     "updateType": "patch",
                     "branchName": "renovate/helmfile-helm/helm-charts/monitoring-helmfile-chart-updates"
                   }
                 ],
                 "packageName": "grafana",
                 "versioning": "helm",
                 "warnings": [],
                 "sourceUrl": "https://github.com/grafana/helm-charts",
                 "registryUrl": "https://grafana.github.io/helm-charts",
                 "homepage": "https://grafana.com/",
                 "currentVersion": "8.5.1",
                 "currentVersionTimestamp": "2024-09-04T17:04:03.867Z",
                 "isSingleVersion": true,
                 "fixedVersion": "8.5.1"
               },

My issue is, I have pulled and pushed all helm-charts used in my environment to private AWS ECR. Therefore my helmfile.yaml & repositories.yaml files are not configured to be utilized as intended by renovate. Example of my current config:

helmfile.yaml:

- name: grafana
  namespace: monitoring
  chart: ecr/grafana
  version: 8.5.1
  installed: true
  values:
    - grafana-values.yaml.gotmpl
    - grafana-values.yaml

repositories.yaml:

repositories:
- name: ecr
  url: {{ .Values.image.repository }}
  oci: true
---

When running renovate with this config, the logs are as follows:

         {
                 "depName": "grafana",
                 "currentValue": "8.5.2",
                 "registryUrls": [],
                 "skipReason": "unknown-registry",
                 "updates": [],
                 "packageName": "grafana"
               },

It would be nice if Renovate can add a feature in the helmfile config of the renovate.json to specify which registryUrls to use regardless of what is shown in the repositories.yaml. I think of it as an override feature. This will allow version updates to still be detected for those who are using private repositories for open-source helm-charts.

[rarkins]

Please try with registryAliases. And if not possible, provide a public reproduction (instructions to follow) which fails in the same way as you get privately.

[mashiofu-cafex]

Resolved this by utilizing registryAliases and renaming helm repository name within helmfile.yaml and repositories.yaml. Grafana example:

- name: grafana
  namespace: monitoring
  chart: ecr-grafana/grafana
  version: 8.5.1
  installed: true
  values:
    - grafana-values.yaml.gotmpl
    - grafana-values.yaml

repositories:
- name: ecr-grafana
  url: {{ .Values.image.repository }}
  oci: true
---

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team