[Frontend] Support custom Secret Detection profiles in existing UI
designs: Design: Advanced Configuration Profiles management (gitlab-org#23403)
prototype: https://security-coverage-prototype-0b2bbb.gitlab.io/security-inventory-profiles/#/security-configuration/enable-scanners
✅ Add a section in the modal (see designs) with titleAdvanced configuration, descriptionSettings passed to the analyzer that override its default behavior., and a table with columnsVariableandValueshowing the custom fields✅ Add a badge next to each profile in the dropdown (see prototype) readingGitLaborCustom✅ Ensure that the default profile always shows first in the dropdown✅ Late-stage tweak: badges should show the root group's name✅ Show all attached profiles for a project instead of just the first one (#631608 (comment 3940331781))
pre-spike description
- Spike — create a custom Secret Detection profile via GraphiQL with
configurable_security_scan_profileson, then walk every surface that renders profiles plus the wizard apply path- Fix must-haves here, file nice-to-haves to #624194
- Surfaces, under
ee/app/assets/javascripts/:security_configuration/components/enable_scanners_wizard/{select_scanners,review}.vuesecurity_configuration/components/scan_profiles/{group_scanners_overview,scanner_details,source_cell,scan_profile_configuration}.vuesecurity_inventory/components/bulk_scanners_update_drawer.vue
- Known must-haves
- Make sure that the default profile appears first in any dropdowns
- Badge recommended vs custom in the wizard dropdown —
gitlabRecommendedis already inscan_profile.fragment.graphql
- Show configuration in
scan_profiles/scan_profile_details_modal.vue- Extend the query to
triggerSettings { configuration { ... on SecretDetectionConfiguration } } - Render read-only:
secure_analyzers_prefix,image_suffix,historic_scan,log_options,excluded_paths,ruleset_git_reference— closed schema, so that is all of them - Hide the section when the resolved configuration is empty
- Extend the query to
Edited by Miranda Fluharty