Allow self-managed to configure auto-disabling hooks
Note #390157 (closed) will allow self-managed to prevent the auto-disabling feature altogether in %15.10. This issue is to explore allowing customers to configure some of the parameters if they have the feature enabled.
Release notes
Problem to solve
In #390157 (closed) we allowed self-managed to prevent the auto-disabling feature altogether.
However, some self-managed customers may want to have auto-disabling hooks, but configure some of the parameters themselves.
Proposal
The simplest admin control to add would be allowing users to raise (or remove) the failure threshold, either greatly extending the grace period (currently 3 failures) or making all failures belong to the grace period. We could also provide access to the back-off parameters (initial duration and growth factors), which some users may wish to tweak.
Making these configurable on an instance level would be the most straightforward - group or project level values for these parameters would be quite a bit trickier.
Potential scenarios by plan:
- SaaS:
- free tier, default settings
- free tier, custom settings
- paid tier, default settings
- paid tier, custom settings
- paid tier, turned off for project/group
- Self-managed
- free tier, default settings
- free tier, custom settings
- paid tier, default settings
- paid tier, custom settings
- paid tier, turned off for project/group
- paid tier, turned off at instance level
MVCs
-
Enable a rails console command to manage the configuration -
Implement UI to manage the settings
Intended users
Self-managed users Administrators This could likely be a Premium or Ultimate feature as the concerns are beyond individual teams.