vRealize Automation Cloud Assembly supports integration with GitLab and GitHub 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 vRealize Automation Cloud Assembly. Also, you must save your blueprints in a specific structure in order for them to be detected by Git. To create an integration with GitLab or GitHub, select Infrastructure > Connections > Integrations in Cloud Assembly and then make the appropriate selection. You will need the url and token for the target repository.

When Git 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 vRealize Automation Cloud Assembly. You can version action scripts either directly to Git, or you can create versions in vRealize Automation Cloud Assembly. If you create a version of an action in vRealize Automation 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 vRealize Automation 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 vRealize Automation Cloud Assembly.

Before you Begin

You must create and save your blueprints in a specific structure in order for them to be detected by GitLab or GitHub.

  • Configure and store Blueprints to be integrated with GitLab correctly. Only valid blueprint are imported into GitLab.
    • Create one or more designated folders for the blueprints.
    • All blueprints must be stored within blueprint.yaml files.
    • Ensure that the top of your blueprints include the name: and version: properties.
  • Extract an API key for the applicable repository. In your Git account, select your login in the upper right corner, and navigate to the Settings menu. Select Access Tokens, then name your token, set an expiration date. Then, select API and create the token. Copy the resulting value and save it.

The following guidelines must be observed for all blueprints 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.