Goal
Use the prebuilt PawSQL repository connector to review SQL on GitLab pushes and merge requests.Before you begin
- Verify connectivity to GitLab SaaS or the enterprise GitLab service.
- Prepare a GitLab credential that can read the target project and publish status.
- Create the PawSQL project, workspace, and review policy.
- Identify the projects, repositories, branches, and SQL paths in scope.
- For self-managed GitLab, prepare the service URL and enterprise CA chain.
Configuration
1
Create the GitLab connection
Choose GitLab in the PawSQL repository connectors, enter the service URL when required, and authenticate.
2
Select projects and repositories
Limit the GitLab groups, projects, or repositories available to the connection.
3
Choose trigger events
Select the required push, merge-request creation, update, or reopen events.
4
Define the SQL scope
Set target branches, directories, file extensions, and exclusions.
5
Map review context
Choose the PawSQL workspace, policy, and gate thresholds for each repository or branch.
6
Validate the connector
Send a test event and confirm job correlation, findings, and merge-request status.
Self-managed GitLab
Validate DNS, proxy, firewall, and TLS between PawSQL and GitLab. Do not disable TLS verification as a permanent workaround for certificate errors.Acceptance criteria
- Only approved GitLab projects and events are processed.
- SQL files and locations are identified correctly.
- The workspace matches the target database.
- The latest revision receives the correct gate status.
- Duplicate events do not create conflicting feedback.
- Credentials and sensitive SQL are absent from logs.
Verification
Confirm a test event creates a correlated job with correct findings and merge-request status.The prebuilt GitLab repository connector is distinct from calling PawSQL in GitLab CI. For a pipeline-controlled workflow, use the OpenAPI pipeline pattern.