Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.maia.ai/llms.txt

Use this file to discover all available pages before exploring further.

This feature is available to customers on specific editions. Visit the Pricing page to learn more about each edition.
Typically, to facilitate a connection between , each Git provider will require authentication. This process is usually via an OAuth mechanism, and requires a small “application” within each Git provider, to allow and control access to the resources within.
Once you connect a project to a Git repository (GitHub, GitLab, Azure DevOps, or Bitbucket), you cannot disconnect or change the Git repository connection.You must create a new project from scratch if you need to:
  • Disconnect from your current Git repository.
  • Connect to a different Git repository.
  • Switch between different repo host platforms (e.g., from GitHub to GitLab).
Reusing an existing Matillion ETL Git repository isn’t supported and can cause issues with your pipelines.
For each Git provider that supports, we provide installation and troubleshooting guides. These can be found below for each provider.

​
Supported providers

Aside from a Matillion-hosted Git offering, the external Git providers that are currently able to be connected to are as follows:

​
GitHub

See how to Install the app for GitHub. When installing the app for GitHub, you must grant read and write access to repository contents (commits, branches, releases, and merges) and GitHub Actions workflow files (.github/workflows/). These permissions enable to manage repositories and update workflows in your repository.

​
Azure DevOps

Instructions for Installing the app for Azure DevOps.

​
GitLab

Connecting GitLab to is a straightforward process. Read about the prerequisites to get started.

​
Bitbucket

Likewise, it is a simple process for connecting Bitbucket to . Ensure you’re ready to go by reading the prerequisites here.

​
Allowing IPs

You may need to allow IP addresses for . Make sure the Hybrid SaaS s and Git repositories IP addresses are allowed on your repository if applicable.

​
How we connect to the Git provider

uses OAuth to connect to your Git provider. The app is registered with the scopes needed for to work. The application has permissions to read and write to the repositories and to read account metadata. In addition, the app honors all user permissions set up by your Git admin. For example, if a user doesn’t have access to a repository in an organization, they won’t be able to use that repository in . This is a standard method of connecting to Git providers, and is the recommended approach for security and ease of use. When a user tries to authorize with one of the Git providers, will redirect the user to the Git provider’s OAuth page, which talks directly with the app that is already installed in the user’s account. At any time, the user can revoke access to the app from their Git provider account. We don’t store any sensitive user information. We only store the user access token that is returned from the Git provider and the refresh token. The user access token is used to allow the user to perform day-to-day actions. The refresh token is used to generate a new token when the token expires. The user access token and the refresh token are stored in the Matillion secure vault. OAuth 2.0 authorization flow