Add secret detection configuration type to GQL mutations

Gal Katzrequested to merge
gkatz_add_secret_detection_type into master

What does this MR do and why?

Adds a typed secretDetection configuration member to the SecurityScanProfileConfigurationInput GQL input, so secret detection scan profiles can carry per-trigger configuration through the create/update mutations. The input mirrors the security_profile_secret_detection_configuration JSON schema. It also extends stripDefaults (default true) to the create mutation to match the update.

Changelog: added
EE: true

Related issue

Add SD configuration values and mapping (#606237 - closed) • Gal Katz

How to set up and validate locally

  1. Enable the FF: Feature.enable(:configurable_security_scan_profiles)
  2. Create a secret detection profile with some configurations for root group g:
mutation {
  securityScanProfileCreate(input: {
    namespaceId: "gid://gitlab/Group/<g.id>",
    scanType: SECRET_DETECTION,
    name: "Secret detection profile for testing",
    description: "This is a test",
    triggers: [{
      triggerType: DEFAULT_BRANCH_PIPELINE,
      configuration: { secretDetection: { imageSuffix: FIPS, historicScan: true, excludedPaths: ["spec/"] } }
    }]
  }) {
    errors
  }
}

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports