Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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.
This page answers frequently asked questions about the managed GitLab ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which GitLab plans does the connector require?
Most tables ingest from any GitLab tier, including Free. The epics, epic_issues, epic_boards, and group_iterations tables require a Premium or Ultimate group. The vulnerabilities and compliance_frameworks tables require Ultimate.
Which tables does the connector support?
The connector supports project, group, repository, CI/CD, and security tables, such as projects, groups, issues, merge_requests, commits, pipelines, deployments, vulnerabilities, and compliance_frameworks. For the full list and destination schemas, see Supported source tables.
How far back can the connector ingest data?
For incremental tables, the first sync ingests records from the configured start_datetime. For its default, see Connector options. Each later sync ingests records modified after the last run. Full-refresh tables reingest all available records on every run.
Which authentication methods does the connector support?
The connector supports OAuth U2M (user authorization). Basic authentication and OAuth M2M are not supported.