## Problem to Solve We want to make it as easy as possible for any customer to enable Secret Detection now that it's availible in core and the configuration page is availible to all users. Similar to the [SAST Configuration Button](https://gitlab.com/groups/gitlab-org/-/epics/3262), we should have a MR button to easily enable Secret Detection.  ## Decisions ### Feature flag The feature will initially be implemented behind the `sec_secret_detection_ui_enable` feature flag (introduced in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57869). ### GraphQL #### `configureSecretDetection` mutation This mutation is triggered when the user clicks on `Configure via a Merge Request` in the Security Configuration page. The API responds with a `successPath` which is the path to the MR that was created. ```graphql mutation configureSecretDetection($input: ConfigureSecretDetectionInput!) { configureSecretDetection(input: $input) { successPath errors } } ``` ## Feature flags ### Active <!-- #### `feature_flag_name` * **Status:** * **staging:** * **production:** * **Purpose:** * **Rollout issue:** * **YAML:** --> #### `sec_secret_detection_ui_enable` * **Status:** * **staging:** Enabled by default. * **production:** Enabled by default. * **Purpose:** Controls whether SAST can be configured via the UI. * **Rollout issue:** https://gitlab.com/gitlab-org/gitlab/-/issues/326049 * **YAML:** [ee/config/feature_flags/development/sec_secret_detection_ui_enable.yml](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/config/feature_flags/development/sec_secret_detection_ui_enable.yml)