Make the Sidekiq job limiter configurable through the admin area
In a first iteration, for the rollout to GitLab.com, we've use env variables to configure the job limiter. To make this available and configurable for self-managed installations. We should make this configurable.
A typical way is to We do have this note on the top of gitlab.yml
discouraging that. This doesn't mean that nothing should go there, but there are good reasons for putting the configurations into database. The advantages of doing it in the database:
- Configurable through the API and web-interface
- More discoverable.
- Does not need the different ways of allowing configuration through
gitlab.rb
(omnibus) or the charts.
We haven't had any setting of the same kind before. Admin Area > General
in the admin setting dashboard is the legitimate location. After updating the setting, we'll need to prompt the user to restart Web and API fleet.
Edited by Bob Van Landuyt