As an administrator, you can configure a connection between your Automation Orchestrator deployment and a Git repository or project.
To use Git for management of your Automation Orchestrator object inventory, you must configure a connection to your Git repository by using the Automation Orchestrator Client.
Note: You cannot add multiple Git repositories from different accounts over SSH because
Automation Orchestrator creates one SSH key for each instance. To add multiple Git repositories, you can add them over HTTP as described in this documentation.
Be aware of the following limitations when using a Git repository with your Automation Orchestrator deployment:
- Only SHA-1 commit hashes are supported.
- SHA-1 commit hash conflict between the internal Git repository and the remote Git repository are possible and are not automatically resolved. In such scenarios, all local changes should be discarded.
- Performing manual changes in the Git repository causes merge conflicts when pulling the remote Git repository in the Automation Orchestrator Client. If the end of line sequence is changed both revisions will appear to be the same, but will always result in a merge conflict that must be resolved.
Prerequisites
- Verify that your Automation Orchestrator environment uses a VMware Cloud Foundation license.
- Generate an access token for your GitLab project and copy it to your clipboard for use during the configuration process. See Creating a personal access token.
Note: For this use case, you are using a GitLab project. If you are more familiar with GitHub, you can use a GitHub repository. For information generating a GitHub token, see Creating a personal access token for the command line.