OCI repoURL for Helm charts in ArgoCD gets picked up as docker image updates

[p4block]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitLab

Please tell us more about your question or problem

Bitnami deprecated https artifacts, so we moved to oci endpoints for the chart repos.

We have apps declared as Application custom resources from ArgoCD and those now create a dependency named "repoURL+chart"

Example with influxdb-release.yaml

  source:
    repoURL: registry-1.docker.io/bitnamicharts
    targetRevision: 6.3.23
    chart: influxdb 

Now creates an MR to update registry-1.docker.io/bitnamicharts/influxdb and broke our custom rules on auto upgrading (that were targeting just "influxdb")

This didn't happen before when repoURL: "https://charts.bitnami.com/bitnami"

I have some ideas on how to fix it, but wonder what would be the correct solution to work around the problem. I think that some config:recommended rule was being at play but is no longer acting.

Logs (if relevant)

No response

[rarkins]

Could you try to edit the above for more clarity? I'm not sure what you're asking.

[p4block]

Let me rephrase
We switched repoURL from "https://charts.bitnami.com/bitnami" (https) to registry-1.docker.io/bitnamicharts (oci) and now package names are detected as registry-1.docker.io/bitnamicharts/package-name instead of just package-name

PR names are like
chore(deps): update registry-1.docker.io/bitnamicharts/influxdb docker tag to v6.5.0

Which now come think of it, it's treating them now as docker images and not helm charts.
chore(deps): update helm release sonarqube to v10.8.0

If I go into Dependecy Dashboard I see they're all under the ArgoCD category in detected dependencies though.

[p4block]

Note that I don't particularly mind that, I just need the detected package name to not include the repo base url. I could do it with a metric ton of custom package groups I think, but something tells me that's not the best approach.

[rarkins]

It's correct that packageName is fully qualified, e.g. like registry-1.docker.io/bitnamicharts/influxdb above. What you see in the PR title is based on depName, which is possible to make different than packageName. I guess in this case it could make sense to call that bitnamicharts/influxdb.

[p4block]

I think there's a bigger problem than aesthetics, charts used to be detected as charts with the old https endpoint but with the oci endpoint the chart is detected as a "docker image update" (and I also get no changelog of the chart)

Iirc it should still be possible to obtain this info from the oci registry, but in any case, they're not docker images (!)

[rarkins]

The fact it says "docker image" is aesthetics. It's from this default config from the docker datasource:

renovate/lib/modules/datasource/docker/index.ts

Line 52 in fc36735

commitMessageTopic: '{{{depName}}} Docker tag',

You could probably override this with packageRules and setting commitMessageTopic.

We could perhaps set up one or more new datasources which are essentially "wrappers" around datasource/docker but which have different config templates.