BE: Add role_approvers to security_orchestration_policy JSON schema
Why are we doing this work
Scan Result Policy Action currently supports individual approvers or a group of users. However, when a customer has projects with lower criticality or the scan results detect a vulnerability of low criticality (I.e., Low/Medium), they want to require an approver from the project based on the role (I.e., owner/maintainer)
This issue focusses on adding the role_approvers
field to security_orchestration_policy JSON schema
Relevant links
Epic: Support Role Based Approval Action for Scan Res... (&8018 - closed)
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
-
backend Update ee/app/validators/json_schemas/security_orchestration_policy.json to add role_approvers
schema:
"role_approvers": {
"type": "array",
"description": "Specifies a list of roles required to approve affected merge request.",
"minItems": 1,
"additionalItems": false,
"items":{
"type": {
"enum": [
"guest",
"reporter",
"developer",
"maintainer",
"owner"
]
},
"minLength": 1
}
}
Verification steps
Edited by Sashi Kumar Kumaresan