Jann Fischer

Oh, I agree, this should be fixed. For the write-back of `.argocd-source-.yaml`, we actually check whether there are differences between the existing and generated file and only perform the commit...

> For kustomize could it check for updates against the image defined in kustomize file? The long term fix will be to migrate to a dedicated API (e.g. make argocd-image-updater...

That sounds like a great idea. I'd not oppose an appropriate PR :)

Hey, there has been a PR on the Argoproj's community maintained Helm chart repository at https://github.com/argoproj/argo-helm/pull/477, but it got closed for reasons unknown to me. It might make sense to...

Can you please elaborate more on the use-cases this would be intended for? In fact, we already know which images are actually running for a given Argo CD application. Probably....

HI @maggiedeuitch, I'm not sure if I understand your use-case correctly. What exactly is the outcome you expect? > Is there configuration that I'm missing that will force image updater...

The case with semantic versioning with certain suffixes is a different one: these strings are a valid semantic version. With prefixes, that's not the case, since the semver spec does...

There is a draft PR which supposedly will implement this: #413

Currently, you can make argocd-image-updater work with a plugin if your plugin makes use of Kustomize. For this to work, you need to set `write-back-method` to `git`, and `write-back-target` to...

Then sorry, not possible yet. It may become possible once the CMP v2 in Argo CD supports parametrization.