Marco Maurer (-Kilchhofer)
Marco Maurer (-Kilchhofer)
Add support to use existing secret for configuring `sshPrivateKey` in `configs.repositories.<name>`.
Hi @tanguynicolas Would you be okay in managing the whole secret content yourself? This structure in the values.yaml only creates a Secret with the content described here: https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-repositories-yaml/ The key...
Add support to use existing secret for configuring `sshPrivateKey` in `configs.repositories.<name>`.
Friendly reminder, @tanguynicolas
Add support to use existing secret for configuring `sshPrivateKey` in `configs.repositories.<name>`.
Alright 👍 I think then you should file a enhancement proposal in [argoproj/argo-cd](https://github.com/argoproj/argo-cd/issues/new/choose) or ask the community on [Slack](https://argoproj.github.io/community/join-slack) in [#argo-cd](https://cloud-native.slack.com/archives/C01TSERG0KZ) or [#argo-cd-contributors](https://cloud-native.slack.com/archives/C020XM04CUW) channel. If you create the connection to...
@DandyDeveloper friendly reminder
@DandyDeveloper another friendly ping 
Friendly reminder @DandyDeveloper
Hi @alex-shef > The main idea is to achieve a single-apply approach. What do you mean in detail? You don't need Terraform afterwards? Just prepare everything and you're good?
And your TF execution environment does not have connectivity to the Kubernetes API (firewall/network and credentials)? If so, I'd use the port-forward method of the provider :)
@alex-shef could you solve your issue?
@onematchfox anything needed from your side?