Cloud Assembly supports integration with Git repositories so that you can store blueprints under source control and automatically download saved blueprints that are associated with designated projects. 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 Infrastructure > Connections > Integrations 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 cannot push new or updated blueprints to the Git repository from Cloud Assembly. Also, you cannot push new blueprints to the repository from Cloud Assembly. To add blueprints to a repository, developers must use the Git interface.

The following guidelines must be observed for all blueprints to be used with Git integration.

  • Each blueprint must reside in a separate folder.

  • All blueprints must be named blueprint.yaml.

  • All blueprint YAML files must use name and version fields.

  • Only valid blueprint are imported.

  • If you update a draft blueprint imported from Git, and its content differs from that in the top version, the draft will not be updated in subsequent syncs and a new version is created. If you want to update a blueprint and also allow further sync's from Git, then you must create a new version after final changes.