GitLab connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for GitLab from the Previews page. See Manage Azure Databricks previews.

The managed GitLab connector in Lakeflow Connect ingests repository, project, group, CI/CD, and security data from GitLab into Azure Databricks.

Feature availability

Feature	Availability
UI-based pipeline authoring	Supported
API-based pipeline authoring	Supported
Declarative Automation Bundles	Supported
Incremental ingestion	Supported
Unity Catalog governance	Supported
Orchestration using Databricks Workflows	Supported
API-based column selection and deselection	Supported
API-based row filtering	Not supported
SCD Type 2	Supported Tables with VARIANT columns (commits, releases, deployments, epics, merge_request_commits, epic_issues, merge_request_discussions) do not support SCD type 2.
Automated schema evolution: New and deleted columns	Supported
Automated schema evolution: Data type changes	Not supported
Automated schema evolution: Column renames	Not supported Requires a full refresh.

Authentication methods

Authentication method	Availability
OAuth U2M	Supported
OAuth M2M	Not supported
Basic authentication (username/password)	Not supported

Ingest from GitLab in 3 steps

Note

Before starting, review the Azure Databricks user persona, supported interfaces, ingestion frequency, and common patterns.

1. Configure GitLab for ingestion (Admins): Set up GitLab to authenticate with Azure Databricks.
2. Create a Unity Catalog connection (Admins): Create a connection in Catalog Explorer to store credentials for Azure Databricks to authenticate with GitLab.
3. Create an ingestion pipeline (Admins or non-admins): Select any supported interface and create a pipeline from an existing connection.