argocd-image-updater updates image spec on changes in git source

[milenpankov]

I am using argocd-image-updater with a digest update strategy, e.g.

argocd-image-updater.argoproj.io/image-list: myapp=bcr.internal.cloud/myapprepo/myapp:test
argocd-image-updater.argoproj.io/myapp.update-strategy: digest
argocd-image-updater.argoproj.io/myapp.helm.image-spec: images.myapp.image

Everything seems to work fine and the image tag hash is updated and the deployment is restarted wherever there is a change and a new image is pushed in the registry.
However wherever there is an update in the git repository, which is the source of the ArgoCD application (for example a new commit pushed), but this change does not affect the application source path itself, the deployment is restarted and the cause seems to be the argocd-image-updater. On every git source change I see in the argocd-image-updater logs that argocd-image-updater is setting new image hash (which is actually the same as the old one) and the deployment gets restarted. It happens to all applications using argocd-image-updater annotations and the git repository as a source.
Such a behavior is not documented anywhere in the argocd-image-updater docs. Is it normal or is it a bug?
These are part of the logs wherever there is a change in the git source:

level=info msg="Setting new image to bcr.internal.cloud/myapprepo/myapp:test@sha256:273356a745f52c490e92be8b41e2b853e34d1deba1e099fdc8221a4b5b83b6d4" alias=myapp application=myapp image_name=myapprepo/myapp image_tag=dummy registry=bcr.internal.cloud
level=info msg="Successfully updated image 'bcr.internal.cloud/myapprepo/myapp:test@dummy' to 'bcr.internal.cloud/myapprepo/myapp:test@sha256:273356a745f52c490e92be8b41e2b853e34d1deba1e099fdc8221a4b5b83b6d4', but pending spec update (dry run=false)" alias=myapp application=myapp image_name=myapprepo/myapp image_tag=dummy registry=bcr.internal.cloud
level=info msg="Committing 1 parameter update(s) for application cx-data-extractor-dev" application=cx-data-extractor-dev
level=info msg="Successfully updated the live application spec" application=myapp

[chengfang]

I don't see a valid reason why unrelated changes in git repo would trigger image updater to run. In your env, is there any argocd webhook that responds to git repo push?

[chengfang]

Which versions of image updater you're seeing this issue with?

[milenpankov]

Hello, I am using version v0.15.2.

[milenpankov]

I have also checked the the ArgoCD webhook and it is not configured to respond to changes in the git source for the project that the applications are part of.

[cjcocokrisp]

I'm currently trying to reproduce this bug and I've set up an environment that is similar to what you described and I'm not experiencing this.

Can you provide a little bit more detail about how your repository is set up and what type of commits/updates are causing this to happen?
Also what Argo CD version you are using?
I also just want to double check that you are using argocd as the write-back method as well.