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:

• GitHub
• GitHub Enterprise Server (GHES)
• GitLab.com
• GitLab (self-managed)
• Azure Repos

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 on-premises Git providers, you must use Groundplexes and the SnapLogic app gateway. Use of Groundplexes with the app gateway eliminates the need to expose IP addresses for communication between the control plane and the on-premises Git provider.

Limitations

The SnapLogic Git Integration has the following limitations:

• Snap Pack and Snaplex assets can't be tracked.
• Per project, up to 1,000 assets can be tracked with Git.
• SnapLogic service accounts can't be used to call SnapLogic Git operation APIs. Instead, use authorized individual user accounts for basic authentication.
• Use of on-premises Git providers requires Groundplexes and the app gateway.

Workflow

To set up the Git Integration:

1. Configure your Git provider as described in the following pages. On-premises providers also require a Groundplex and the app gateway.
   • Azure Repos
   • GitHub
   • GitHub Enterprise Server (GHES)
   • GitLab.com
   • GitLab self-managed
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.

Once configured and authorized, use Git operations to meet your organization's processes and requirements. The following pages describe common use cases:

• How to manage separate SnapLogic Environments for development and production.
• How to track assets with a repository
• How to manage concurrent development
• How to use individual Git operations

Repository visibility

Large enterprises typically have many repositories. We recommend making only the repositories for SnapLogic assets visible in Designer and 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:

• For Azure Repos: In Azure DevOps Organization settings, turn off the Third-party application access via OAuth setting.
• For GitHub or GHES: The SnapLogic App registration or the App registration you create provides controls to select specific repositories.
• For GitLab cloud (gitlab.com) or self-managed GitLab: GitLab doesn't offer a way to filter repository visibility. You can use the Git Integration settings in SnapLogic Manager or Admin Manager instead. The Namespaces field determines which repositories are visible to pipeline developers.