Customize the minimum number of vulnerabilities will be considered for approval
Why are we doing this work
Currently Vunerability-check rule applies to one or more vulnerabilities. Providing a way to define the minimum number of vulnerabilities should be considered will give the user more granularity.
Relevant links
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
-
frontend Add a textbox (similar to Approvals required
) with the minimum number of vulnerabilities -
frontend default to 1
to keep support with the current behaviour -
backend Extend the model to support the number of vulnerabilties related to endpoint: http://HOST/api/v4/projects/PROJECT_ID/approval_settings/rules
-
backend Extend or derive the related rules to consider the severities. -
documentation Update related docs
Edited by Zamir Martins