RFC: Implement Unicorn hooks that are settable from within Gitlab source codes - RFC
What does this MR do?
Allow some control over what can be run in Unicorn hooks from within Gitlab source code.
Why was this MR needed?
Currently, Unicorn Hooks can only be effectively set from within Omnibus codebase. While this works great for some environment-specific options, there is some code, like Prometheus configuration that is common to all environments.
This MR is a proposal of a solution so that changes to some Unicorn hooks can be done by only implementing them within one codebase.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
TODO: add changes to Omnibus so that hooks will actually work -
TODO: Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by Backend -
Has been reviewed by Build team
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together
/cc: @marin @nick.thomas