Automation Suite integrates GitOps methodologies (powered by ArgoCD) to automate the deployment, synchronization, and lifecycle management of platform microservices using Git repositories as the source of truth. When utilizing private repositories to protect proprietary configurations and sensitive parameters, the GitOps engine must authenticate to the remote repository. This requires configuring valid access credentials within the GitOps tool, typically using private SSH deploy keys, personal access tokens (PAT), or HTTPS credentials. These credentials allow ArgoCD to clone repositories, read Helm charts, detect branch drift, and apply configurations automatically. Exposing internal company configurations by making repositories public or attempting to co-locate Git servers on cluster nodes violates enterprise security standards. (Reference: UiPath Automation Suite GitOps Deployment Guide – ArgoCD Private Repository Access).
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit