Cloud Assembly supports integration with Git repositories so that you can manage blueprints and action scripts under source control. This functionality facilitates auditing and accountability of processes around deployment.
You must have an appropriate local Git repository configured with access for all designated users in order to set up Git integration with Cloud Assembly. Also, you must create a save your blueprints in a specific structure in order for them to be detected by Git. To create an integration with GitLab, select in Cloud Assembly. You will need the url and token for the target repository.
When GitLab integration is configured with an existing repository, all blueprints associated with selected projects become available to qualified users. You can use these blueprints with an existing deployment or as the basis of a new deployment. When you add a project, you must select some properties regarding where and how it is stored in Git.
You can save actions to a Git repository directly from Cloud Assembly. You can version action scripts either directly to Git, or you can create versions in Cloud Assembly. If you create a version of an action in Cloud Assembly, then it is automatically saved to Git as a version. Blueprints are a bit more complicated, because you cannot directly add them to a Git integration from Cloud Assembly. You must save them directly to a Git instance, and then you can retrieve them from Git when working with the blueprint management page in Cloud Assembly.