Clean-up feature-flag git_abuse_rate_limit_feature_flag & keep code
What does this MR do and why?
- Removes feature flag
git_abuse_rate_limit_feature_flag
and keeps the code. -
git_abuse_rate_limit_feature_flag
was used to toggle theGit abuse rate limit
settings in the Admin > Reporting page. The settings will now be displayed to all instance-level admins.
Screenshots or screen recordings
How to set up and validate locally
- Log-in as
root
and configureGit abuse rate limit
settings onhttp://localhost:3000/admin/application_settings/reporting
. Set
Number of repositories = 1
Reporting time period (seconds) = 300
Send notifications to - root
Toggle-on - Automatically ban users from this application when they exceed the specified limits
- Try to clone any two private repositories as another user. When cloning the second repository, you should receive a 403 error and the user should get banned.
- The admin can disable the setting by setting either
Number of repositories
orReporting time period
to 0. - You can then try unbanning the user from
http://localhost:3000/admin/users?filter=banned
and cloning the repos again.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #394996 (closed)
Edited by Hinam Mehra