Incompatibility with Argocd when using s3 plugin for Argocd applications

[devopsoch]

Describe the bug We are currently using the plugin s3 in our Argocd applications to deploy our charts. When we were trying to integrate Argocd image updater using git write back method, we got an error says that Argocd image updater could not access the URL to the repo, so he can not commit the changes.

The problem is that in our applications manifests we set the filed spec.source.repoUrl pointing to our repository of helm chart which is the s3 bucket.

What I could understand that is Argocd image updater was trying to use the URL located in that filed to push the new image tag, but actually the URL was pointing to S3 bucket which not the right place to push.

To Reproduce Steps to reproduce the behavior:

1. Create an application which use s3 bucket as registry for helm charts & set the repoUrl filed to the s3 URL.
2. Add these annotations to the applications:

• argocd-image-updater.argoproj.io/image-list: ms=nginx/nginx
  

• argocd-image-updater.argoproj.io/ms.force-update: 'true'
  

• argocd-image-updater.argoproj.io/ms.update-strategy: latest
  

• argocd-image-updater.argoproj.io/write-back-method: "git"
  

3. Create the applications
4. push new tag

Additional context I tried that with the default write back method it works, Argocd image updater could update the image, but the problem is that our sync policy is set to AutoSync so Argocd detect a drift change and re-sync the existing values in GIT and so on ....

Version v0.12.0

Logs Could not update application spec: could not get creds for repo 's3://repo.bucket/charts/': credentials for 's3://repo.bucket/charts/' are not configured in Argo CD settings