Add 'License-Check' approval rule to enforce license compliance policy.
requested to merge 13538-license-compliance-approvals-in-merge-request-mvc-add-license-check-approval-rule-to-backend-code-to-enforce-policy into master
What does this MR do?
This change allows users to block a merge request if a new dependency brings in a license that violates the license compliance policy.
To activate this feature you must:
- Create a new Merge Request Approval Rule named
License-Check.
- Blacklist software licenses.
- Submit a Merge Request that brings in a dependency that violates the license compliance policy.
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Performance and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods - [-] Security reports checked/validated by a reviewer from the AppSec team
Related Issues
Edited by 🤖 GitLab Bot 🤖