Helm repository unsupported protocol scheme "acr"

[gaoshuai2020]

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a
question in argocd slack channel.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

Seems Argo CD does not support to add helm repository with protocal: "acr".
Does Argo CD only support to add 'http' or 'https' helm repository?

To Reproduce

Try to add a helm repository with protocal "acr". For example: "arc://example.com"

Expected behavior

Helm repository could be added successfully.

Screenshots

Version

argocd: v1.7.1+da5fa74
  BuildDate: 2020-08-26T21:13:01Z
  GitCommit: da5fa74ca1bf9e025dcfe3c8cac083da1b7b45c8
  GitTreeState: clean
  GoVersion: go1.14.1
  Compiler: gc
  Platform: darwin/amd64
argocd-server: v1.7.3+b4c79cc
  BuildDate: 2020-09-01T23:19:02Z
  GitCommit: b4c79ccb88173604c3786dcd34e83a9d7e8919a5
  GitTreeState: clean
  GoVersion: go1.14.1
  Compiler: gc
  Platform: linux/amd64
  Ksonnet Version: v0.13.1
  Kustomize Version: {Version:kustomize/v3.6.1 GitCommit:c97fa946d576eb6ed559f17f2ac43b3b5a8d5dbd BuildDate:2020-05-27T20:47:35Z GoOs:linux GoArch:amd64}
  Helm Version: version.BuildInfo{Version:"v3.2.0", GitCommit:"e11b7ce3b12db2941e90399e874513fbd24bcb71", GitTreeState:"clean", GoVersion:"go1.13.10"}
  Kubectl Version: v1.17.8

Logs

Unable to connect HTTPS repository: Get "acr://xxx/index.yaml": unsupported protocol scheme "acr"

[jessesuen]

In order to support this I think

1. ACR plugin needs to be configured on repo-server like so:
   Helm S3 Support #2558 (comment)

2. Argo CD needs to support different scheme and fork helm binary to query index.yaml

[jonathanendy]

vote for this also, I'm trying to add helm repo on GCS with the prefix gs://

[aweris]

For future readers:

I had same issue with GCS repo. I used chartmuseum as helm repo proxy and configured helm repo URL as http://<svc-name>.<namespace>.svc.cluster.local:8080

[artem-kosenko]

For future readers:

I had same issue with GCS repo. I used chartmuseum as helm repo proxy and configured helm repo URL as http://<svc-name>.<namespace>.svc.cluster.local:8080

I was fining with the S3 for Helm Charts and is works only over HTTPS protocol, so index.yaml must be public, that absolutely not appropriate for private repository. The workaround with the chartmuseum as a helm proxy works perfect! Thank you for your little commit there, it save me a lot of time :)
actually it allow configure the SSL and base authorization with some username and password, but it is secure enough, in case you do not create an ingress for the chartmuseum app and access it only inside the cluster