Datahelpers and Throttle Services for Git abuse rate limiting
requested to merge git-abuse-rate-limiting-alerted-users-datahelpers-and-throttle-services into master
What does this MR do and why?
This MR adds the backend part for the alerted users feature for Git abuse rate limiting.
MR's for this feature (in order of dependency):
- Database and API for Git abuse rate limiting al... (!110760 - merged)
- Datahelpers and Throttle Services for Git abuse... (!110762 - merged) (current)
- Frontend for Git abuse rate limiting alerted users (!110759 - merged)
Issue: https://gitlab.com/gitlab-org/modelops/anti-abuse/team-tasks/-/issues/186+
Screenshots or screen recordings
Admin settings | Group settings | |
---|---|---|
Before | ||
After |
How to set up and validate locally
- Cherry pick all commits from the MR's mentioned in the description (alternatively, checkout the
add-alerted-users-to-git-abuse-rate-limiting
branch, which has them all) - Enable the feature flag
Feature.enable(:git_abuse_rate_limit_feature_flag)
- Visit the
Git abuse rate limit
admin settings:http://localhost:3000/admin/application_settings/reporting
- Add and/or remove users from
Send notifications to
field - Click
Save changes
- Visit the
Git abuse rate limit
group settings:http://localhost:3000/groups/${group_name}/-/settings/reporting
- Add and/or remove users from
Send notifications to
field - Click
Save changes
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.
Edited by Alex Buijs