Update helm chart version dependency

[hemersonlcosta]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

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

Hi everyone,

I'm working on a project where the configuration setup is a bit unusual. Each Helm chart in my project has its own environment file that specifies dependency versions. I'm currently managing the New Relic Helm chart, which includes several dependencies.

One specific issue I'm facing is with the "k8s-events-forwarder" image, which is a dependency from the nri-kube-events chart. When configuring the regexManagers to obtain the Docker image version, it pulls the latest version, rather than the specific version indicated in the values file.

How can I configure the regexManagers to ensure it correctly identifies and uses the dependency version from another Helm chart's values? Here's the link.

Thanks for your help!

This is mine regexManagers

{
"fileMatch": ["^newrelic/newrelic-initialize-variables\.sh$"],
"matchStrings": [
"export NEWRELIC_K8S_EVENT_FORWARDER_TAG="(?<currentValue>\S+)""
],
"datasourceTemplate": "docker",
"depNameTemplate": "newrelic/k8s-events-forwarder",
"versioningTemplate": "semver"
},

This is my initialize-variables.sh

export NEWRELIC_REPO="newrelic"
export NEWRELIC_REPO_URL="https://helm-charts.newrelic.com"
export NEWRELIC_SOURCE_REGISTRY="docker.io"
export NEWRELIC_PROMETHEUS_SOURCE_REGISTRY="quay.io"
export NEWRELIC_CHART_VERSION="5.0.74"
export NEWRELIC_CHART_NAME="nri-bundle"
export NEWRELIC_INFRA_IMAGE="newrelic/infrastructure-bundle"
export NEWRELIC_INFRA_TAG="3.2.37"
export NEWRELIC_KUBE_EVENTS_IMAGE="newrelic/nri-kube-events"
export NEWRELIC_KUBE_EVENTS_TAG="2.9.5"
export NEWRELIC_PROMETHEUS_AGENT_IMAGE="newrelic/nri-prometheus"
export NEWRELIC_PROMETHEUS_AGENT_TAG="2.21.0"
export NEWRELIC_PROMETHEUS_CONFIGURATOR_IMAGE="newrelic/newrelic-prometheus-configurator"
export NEWRELIC_PROMETHEUS_CONFIGURATOR_TAG="1.15.0"
export NEWRELIC_PROMETHEUS_IMAGE="prometheus/prometheus"
export NEWRELIC_PROMETHEUS_TAG="v2.37.8"
export NEWRELIC_METADATA_INJECTION_IMAGE="newrelic/k8s-metadata-injection"
export NEWRELIC_METADATA_INJECTION_TAG="1.26.4"
export NEWRELIC_KUBERNETES="newrelic/nri-kubernetes"
export NEWRELIC_KUBERNETES_TAG="3.28.3"
export NEWRELIC_K8S_EVENT_FORWARDER="newrelic/k8s-events-forwarder"
export NEWRELIC_K8S_EVENT_FORWARDER_TAG="1.52.0"
export NEWRELIC_KUBE_STATE_METRICS="kube-state-metrics/kube-state-metrics"
export NEWRELIC_KUBE_STATE_METRICS_TAG="v2.12.0"
export NEWRELIC_FLUENTBIT_OUTPUT="newrelic/newrelic-fluentbit-output"
export NEWRELIC_FLUENTBIT_OUTPUT_TAG="1.19.2"

Minimal reproduction

https://github.com/hemersonlcosta/renovate-minimal-reproduction

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[rarkins]

Currently the custom manager can only extract dependencies from one file at a time. Does your requirement need it to fetch from more than one and combine the results into a single dependency?

[hemersonlcosta]

This is mine reproduction, please let me know if you have any else information
https://github.com/hemersonlcosta/renovate-minimal-reproduction

[viceice]

404, please follow our instructions to create a minimal reproduction (see other discussion answer)

[hemersonlcosta]

Sorry my mistake, my first time using it.
Please see link bellow and also on the top of discussion.
Minimal reproduction.

[hemersonlcosta]

Hi @viceice @rarkins
Any comment about my configuration?
Thank you.

[rarkins]

It's not minimal. Please don't @ us

[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.

Good luck,

The Renovate team

[github-actions[bot]]

Hi there,

This is intended as a polite, automated request that users avoid @ mentioning repository maintainers like @rarkins or @viceice. Doing so causes annoying mobile notifications and makes it harder to maintain this repository.

We know it might be common elsewhere but we participate in hundreds of discussions a week and would need to turn off GitHub mobile notifications if we were mentioned in every one.

As a general rule, we will read and respond to all discussions in this repository, so there is no need to mention us.

Thanks, the Renovate team