GitLab CI scanner parameters

The TAS Integrator GitLab CI scanner accepts parameters that control connection settings, project or group selection, endpoint discovery, and output formatting. Understanding these parameters helps you customize scans for different environments and output requirements.

Table 1. Required parameters
Parameter Description

gitlab_url

GitLab instance base URL, such as https://gitlab.example.com or https://gitlab.com.

Table 2. Optional connection parameters
Parameter Description

auth_env

Environment variable name containing the GitLab personal access token with read_api scope or higher. Example: GITLAB_READ_API_TOKEN. Generate tokens in GitLab at User Settings Access Tokens. If not provided, the scanner attempts unauthenticated access, which only works for public projects on public GitLab instances.

auth_file

File path containing the GitLab personal access token. Alternative to auth_env for token authentication.

project

Numeric project ID to scan. Find the project ID in the GitLab web interface under Settings General. Specify either project or group, not both.

group

Numeric group ID to scan. The scanner scans all projects in the group. Find the group ID in the GitLab web interface under Settings General. Specify either project or group, not both.

namespace

Kubernetes or OpenShift namespace where Red Hat Trusted Artifact Signer is deployed. If provided and kubectl is available, the scanner automatically discovers endpoint URLs from custom resource status fields.

Table 3. Optional endpoint override parameters
Parameter Description

rekor_url

Override Rekor endpoint URL. Example: https://rekor.tas.example.com. If not provided, the scanner attempts auto-detection from environment variables, Kubernetes custom resources, or RHEL configuration files.

fulcio_url

Override Fulcio endpoint URL. Example: https://fulcio.tas.example.com.

tuf_url

Override TUF endpoint URL. Example: https://tuf.tas.example.com.

tsa_url

Override Timestamp Authority endpoint URL. Example: https://tsa.tas.example.com/api/v1/timestamp. Ensure the URL includes the /api/v1/timestamp path suffix.

oidc_issuer

Override OIDC issuer URL. Example: https://keycloak.example.com/auth/realms/trusted-artifact-signer.

oidc_client_id

Override OIDC client ID. Example: trusted-artifact-signer.

Table 4. Optional output parameters
Parameter Default Description

output

display

Set output mode. Valid values: display (show in conversation), save (write to file), or both (show and save).

format

markdown

Set output format. Valid values: markdown or yaml.

output_path

Auto-generated

File path for save and both output modes. If not provided, the scanner generates a path based on the scan timestamp and CI/CD platform. Example: gitlab-ci-integration-blueprint-20260903-143022.md.

Example invocations

Scan a project with auto-detected endpoints
/tas-integrator:scan-gitlab

gitlab_url: https://gitlab.example.com
auth_env: GITLAB_READ_API_TOKEN
project: 12345678
namespace: trusted-artifact-signer
Scan a group with explicit endpoints
/tas-integrator:scan-gitlab

gitlab_url: https://gitlab.com
auth_env: GITLAB_READ_API_TOKEN
group: 87654321
rekor_url: https://rekor.tas.example.com
fulcio_url: https://fulcio.tas.example.com
Save the blueprint to a file in YAML format
/tas-integrator:scan-gitlab --output=save --format=yaml

gitlab_url: https://gitlab.example.com
auth_env: GITLAB_READ_API_TOKEN
project: 12345678