Map Dependency Scanning configuration values to CI variables [2/4]

rossfuhrmanrequested to merge
rfuhrman/629403-ds-config-2-mapping into master

What does this MR do and why?

Stacked MR 2 of 4 implementing work item #629403. Targets the branch of MR 1 (rfuhrman/629403-ds-config-1-schema); review and merge that MR first.

Adds the dependency_scanning entry to Security::ScanProfiles::Configuration::CiVariables::MAPPINGS, translating each allowed configuration value into the CI/CD environment variable the Dependency Scanning analyzer reads.

Implementation notes

  • Environment variable names were taken from the Dependency Scanning v2 template (lib/gitlab/ci/templates/Jobs/Dependency-Scanning.v2.gitlab-ci.yml) as the source of truth. Note one discrepancy with the work-item table: the table lists DS_PIPCOMPILE_LOCKFILE_NAME_PATTERN but the template reads DS_PIPCOMPILE_LOCKFILE_FILE_NAME_PATTERN — this MR uses the template's name. Please confirm.
  • Numeric values (max_depth, api_timeout, api_scan_download_delay) are serialized to strings for the environment variable.

Related to

Related to #629403

MR acceptance checklist

  • I have evaluated the MR acceptance checklist for this MR.

🤖 Generated with Claude Code

Merge request reports