馃帹 Design: API fuzzing: project level configure edit route
Background
This is the follow-up to the issue of "project-level configure with local(project) profile"(#330481 (closed))
In the previous issue, we remove the edit route and using beaver token part. This issue is adding the route info back to enable more advanced settings:
- allow multiple routes -> each route has its own check group
JTBD
When I am configuring a CI/CD security scan, I want to specify which assets need to be scanned and under which circumstances, So that I can ensure my assets are secure prior to or at their release.
Target Persona
This user is focusing on the personas:
those who use group-level profiles
Scenario
This issue is focused on the following scenario:
Sometimes in a project, I have a different code base or different area, I want to enable different scan settings. I want to set up different routes with different check groups. So I can make sure certain the areas get a deep scan; other areas can be fast scan.
Tasks
- task 1: Edit route info
- task 2: create more than one route with a different check group