Prevent from enabling more than X policies for given type in security policy project
Summary
- A user can enable more security policies than there is a limit for
- They cannot create new ones due to #411854 (comment 1817021594), but they can enable existing policies
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)
Possible fixes
-
frontend inject maxActiveScanExecutionPoliciesReached
,maxActiveScanResultPoliciesReached
,maxScanExecutionPoliciesAllowed
, andmaxScanResultPoliciesAllowed
into editor_layout.vue and disable the enabled radio buttons -
frontend add tooltip
Edited by Alexander Turinske