GitLab

GitLab is a DevOps platform for hosting Git repositories, managing issues and merge requests, and running CI/CD pipelines.

Bruin supports GitLab as a source for Ingestr assets.

Configuration

Step 1: Add a connection to .bruin.yml

connections:
    gitlab:
        - name: 'my-gitlab'
          access_token: 'glpat-xxx'

• access_token: a GitLab personal access token with the read_api scope.
• base_url (optional): API base URL for self-managed instances, including the /api/v4 suffix (e.g. https://gitlab.example.com/api/v4). Defaults to https://gitlab.com/api/v4.

Step 2: Create an asset file

name: public.gitlab
type: ingestr

parameters:
  source_connection: my-gitlab
  source_table: 'issues'
  destination: postgres

• source_connection: the GitLab connection defined in .bruin.yml.
• source_table: the GitLab table to ingest (see below).

Available Source Tables

GitLab source allows ingesting the following resources:

Table	PK	Inc Key	Inc Strategy	Details
projects	id	updated_at	merge	Projects the token is a member of.
groups	id	–	replace	Groups the token is a member of.
users	id	–	replace	Users visible to the token. On gitlab.com this is the global public directory; intended for self-managed/admin tokens.
issues	id	updated_at	merge	Issues created by the authenticated user.
merge_requests	id	updated_at	merge	Merge requests created by the authenticated user.

Note: GitLab objects carry both a global id and a project-scoped iid. ingestr keys on the global id. Nested fields such as labels, assignees, and references are preserved as JSON, and description fields remain Markdown strings.

Warning — users on gitlab.com: a regular token has no personal scoping on the /users endpoint, so on gitlab.com it returns the entire public user directory and the connector will page through all of it. This table is intended for self-managed / Dedicated instances with an admin token, where /users returns that instance's own user list.