FE: Add component specific filters to Scan Result Policies for License Approval rules in Policy Editor
Why are we doing this work
We are adding specific component filters
option for scan result policies
for license approval rules
This feature should be both implemented on project
and group
level
First iteration should only include free input for components, autocomplete can be added in next iterations ( &10203 (comment 1505306873))
Component => is a combination of both the package and version
Relevant links
- See epic for more information
Design
Designs are attached in parent epic
First iteration should only include free input for components, autocomplete can be added in next iterations ( &10203 (comment 1505306873))
Non-functional requirements
-
Documentation: -
Testing:
Implementation plan
-
frontend create vue component
for filtering licence components inscan_result_policy
policy folder similar toopolicy_rule_branch_selection.vue
. New component should contain adropdown
with available options and free forminput
field forlicence components
. Input field is only visible withany component except
andspecific components
options. -
frontend Update sentence in license_scan_rule_builder.vue
so it can display in licence filter component -
frontend Make sure, state is preserved when user switches between rule
mode andyaml
mode. When user adds component exceptions inyaml
mode, it is properly parsed and validated in input field of new filter inrule
mode
Verification steps
- Upload a GitLab Ultimate license
- Navigate to a project => Security & Compliance => Policies => New policy => Scan result Policy
- Select
licence scan type
, make sure new filter is in place, select some option - Make sure
yaml
is updated correctly - Switch between modes, make sure input is preserved and validated in both modes
- Verify same flow for editing existing
scan result policy
- Verify both on
project
andgroup
level
Edited by Artur Fedorov