Open trv-jsmith10 opened 2 years ago
nbjohnson
commented
2 years ago I would also appreciate adding credential support. My use case needs the extension.tar to be in a secured git repository. Being able to provide a secret name to pull git credentials from to retrieve an extensions.tar from a private repo in Github/Gitlab would be greatly appreciated.
kingsquirrel152
commented
1 year ago I am also very curious about this/would love to be able to pull from a private GHE instance. Looking at other argo services in the ecosystem it appears mTLS is the auth method to connect?
What I am wondering is would it be possible to connect to the argocd API and capture auth credentials in a conical fashion?
Describe the bug
There is no provision to specify credential secret to provide credentials to get the extension.tar file located in nexus repo.
apiVersion: argoproj.io/v1alpha1 kind: ArgoCDExtension metadata: name: hello-world finalizers:
Related helm chart argo-cd
To Reproduce in argo-cd helm -> Values.yaml -> server -> extensions: -> contents: scenario 1: There is no provision in argo-cd helm values.yaml (in extensions: section) to specify secrets if we have to fetch extension.tar file from nexus. (Our organization does not allow to put .tar file in github repo so we have to store the extension.tar file in nexus and read it from nexus) ex:- in the above mentioned manifest, how to read extension.tar from nexus using nexus pull secret
scenario 2: where and how to specify credentials secret if we have to read extension ui folder from github PRIVATE repo? ex:- in the above mentioned manifest, if "argocd-example-extension.git" is in private github repo, how to provide github auth creds
Expected behavior: Expecting secrets provision in argo-cd values.yaml for extension source for git and web options