SnapLogic Git Integration

The SnapLogic Git Integration supports tracking and updating SnapLogic assets in a Git repository.

The SnapLogic Git Integration feature enables Git management of project assets from the SnapLogic UI or with SnapLogic Public APIs. The Git Integration supports the following Git platform providers:

The SnapLogic control plane connects to the Git provider to coordinate Git operations for the cloud-based providers: GitHub, GitLab.com, and Azure Repos.

On-premises installations for GHES and self-managed GitLab typically aren't configured to accept requests from outside the firewall. For these providers, you must use the SnapLogic App Gateway and exactly one Groundplex per environment — which can include multiple nodes — to perform Git operations. The App Gateway eliminates the need to expose IP addresses for communication between the control plane and the on-premises Git provider.

Bitbucket Data Center is also self-hosted, but it doesn't use the App Gateway. SnapLogic connects to it directly over HTTPS, and over SSH when your Bitbucket admin disables basic authentication for API calls. Your network must allow outbound connections from your Cloudplex or Groundplex to the Bitbucket host and SSH port, as described in Configure Atlassian Bitbucket Data Center and the Git Integration.

Limitations

The SnapLogic Git Integration has the following limitations:

  • The Git Integration can't track Snap Pack and Snaplex assets.
  • The Git Integration can track up to 1,000 files in each project. The count includes every tracked asset, because the Git Integration stores each asset as one file, plus any other files in the project's folder in the repository, such as a README. When you associate a repository with a project space, each project in the space has its own 1,000-file limit.
  • Each file can be up to 50 MB.
  • You can't use SnapLogic service accounts to call SnapLogic Git operation APIs. Instead, use authorized individual user accounts for basic authentication.

Get started

To set up the Git Integration:

  1. Configure your Git provider as described in the following pages. On-premises providers (GHES and self-managed GitLab) also require a Groundplex and the app gateway.
  2. Individual users authorize SnapLogic to access their Git provider account. They must have read and write access to the appropriate Git repositories and SnapLogic projects.

After you configure and authorize the Git Integration, use Git operations to meet your organization's processes and requirements. The following pages describe common use cases:

Repository visibility

Large enterprises typically have many repositories. We recommend making only the repositories for SnapLogic assets visible in Designer and Project Manager. This provides the following benefits:

  • Better performance because the SnapLogic APIs don't need to traverse as many remote resources.
  • Fewer repositories show up on the Git menu items, making it easier for pipeline developers to choose the correct location for their assets.

The mechanism to set repository visibility for third-party apps differs between Git providers: