Alberto Chiusole

It took me a while to figure out that I was missing the helm parameter names that instruct ArgoCD on what Helm values to update, see https://argocd-image-updater.readthedocs.io/en/stable/configuration/images/#specifying-helm-parameter-names ```yaml argocd-image-updater.argoproj.io/write-back-method: argocd...

Had to add helm parameters to get it to work, see my comment here: https://github.com/argoproj-labs/argocd-image-updater/issues/431#issuecomment-1471871799

Hello, I just got bitten by this too.. @gjenkins8 did you have any luck debugging this? For anyone interested in working on this, I created the smallest reproducible I could...

I just tried the latest [helm 3.14 release](https://github.com/helm/helm/releases/tag/v3.14.0), and it solved the problem, at least my usecase! :tada: I'd guess that the bit that solved it was that > Allow...

Hi @aboe76, I'd like to extend the example further with a pipenv section. Feel free to comment my fork.

@aboe76 any news?

Hi, I'm still interested in developing that formula; I'll try to find time this week.

I tried updating the image on the argocd-image-updater we use to the one built from this branch. If I keep using the argocd-i-u 0.9.3 helm chart it works fine, but...

I also face the same problem, even when I use `--ignore-paths` subcharts are linted. Here's a run without any paths to ignore: ```console $ kube-linter lint . KubeLinter v0.6.4-0-g4f0b1e01fd ......

Any possible development on this?