Replace DAST profiles input fields with DAST profiles selector
What does this MR do and why?
Describe in detail what your merge request does and why.
This MR resolves 390179
UX was adjusted and confirmed in this comment
Final goal is to allow user to select scanner and site DAST profiles from a list of existing profiles on project level.
On-demand-scans form and DAST configuration already have dast_profiles_drawer with list of profiles and form for creating it.
It can be re-used for scan execution policies.
There are several steps for this migration:
| Description | MR |
|---|---|
| Extract more methods computed and apollo client so it can be re-used for SEP too | MR Link |
| Add profiles selector for Scan Execution Policies for project level and input fields for group level |
|
| Refactor mixin to a composable after Vue is migrated to version 2.7. | Issue link |
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Project level
| Description | Video |
|---|---|
| Selection | selecting |
| Switching between modes | parsing |
| Error handling | error |
Group level
| Description | Video |
|---|---|
| Selection | group_level |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Go to
Security & Complience->Policies->New policy->Scan Execution Policy(security/policies/new?type=scan_execution_policy) - In
Actionssection you can select profiles for DAST scanner - Check that selecting of profiles is working. Try to add new profile, edit existing, select profile, or cancel changes after editing something
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #390179 (closed)