GitLab

Keep rules, alerts and contracts in git, and see what a merge request will touch before it merges.

What Nistor collects

• Repositories as nodes on the graph.
• Provenance: which deploy created or changed an asset ("Deployed by").

What it can run

• GitOps sync: Nistor can pull rules from your repository (off by default). Rules, alerts and contracts can also be pushed from CI with the Nistor CLI; that path does not need this connector.
• MR bot (off by default): each merge request gets a comment listing the affected nodes, rules, open incidents and the estimated change in BigQuery cost, plus the quality checks it touches with Data quality (Enterprise).
• Rule requests (off by default): a request made in Nistor becomes a merge request for review.

Set it up

This integration is in preview. Create a project access token for the repositories Nistor should read and comment on; the README in the repository lists the scopes.