Not working with extra registry parameter in helm value.

[crazy-canux]

Describe the bug

when there are three parameters in helm value, it's not working.

To Reproduce

    argocd-image-updater.argoproj.io/image-list: myalias=my-registry/my-repository:latest
    argocd-image-updater.argoproj.io/myalias.update-strategy: digest
    argocd-image-updater.argoproj.io/myalias.force-update: true
   argocd-image-updater.argoproj.io/myalias.helm.image-name: backstage.image.repository
   argocd-image-updater.argoproj.io/myalias.helm.image-tag: backstage.image.tag

in helm value:

    backstage:
        image:
            registry:
            repository:
            tag:

Expected behavior
update image in argocd.

Additional context
without image-name and image-tag annotation, will get another issue.
new image detected, but not updated in argocd.

time="2024-12-18T09:57:48Z" level=info msg="Successfully updated image 'my-registry/my-repositor@dummy' to 'my-registry/my-repository@sha256:2defa431dcf22d2baf5d4b6d8241caf12d7ad4f09a9168f65327bd80af6e235f', but pending spec update (dry run=false)" alias=myalias application=test image_name=my-repository image_tag=dummy registry=my-registry

Version
0.15.0

Logs

with image-name and image-tag annotation, the image url will include registry which not right.

Failed to pull image "my-registry/my-registry/my-repository:latest@sha256:292638896047d855da3c2f531ccecd0e172a06344840bebf5c2d7d59c36c2e08": rpc error: code = NotFound desc = failed to pull and unpack image "my-registry/my-registry/my-repository@sha256:292638896047d855da3c2f531ccecd0e172a06344840bebf5c2d7d59c36c2e08": failed to copy: httpReadSeeker: failed open: could not fetch content descriptor sha256:292638896047d855da3c2f531ccecd0e172a06344840bebf5c2d7d59c36c2e08 (application/octet-stream) from remote: not found

[chengfang]

Please upgrade to the patch release 0.15.1, which contains important bug fixes. It may not fix this issue but will prevent future errors.

[chengfang]

Without this backstage.image.registry parameter in helm values, does everything work fine?

[leezhihui]

removed backstage.image.repository and it works, so there has default ?

[MaksimKlepikov]

Would be nice to have an option for the registry parameter.
My use case is that I have charts with these values:

image:
  registry: my.private.registry/some-sub-path
  repository: feature-123
  tag: e54096ea

So with image-name, image-tag annotations the image-updater of course writes back this:

image:
  registry: my.private.registry/some-sub-path
  repository: my.private.registry/some-sub-path/feature-123
  tag: new-tag-value

[MaksimKlepikov]

Although in this and this examples I see the use of the registry parameter.
Though proof-of-work with configured image-name, image-tag annotations are not presented in the commit history.
Are these examples correct and supposed to work?