[Admin Panel Setting 3/4] Backend logic for the logging field variation setting
What does this MR do and why?
This is the second MR to split up the changes of !233809 (closed).
The overall approach is to introduce a new application setting that will be controlled via GitLab and be consumed by several services to change the logging fields they emit. With this approach we enable a fast internal migration while giving customers the chance to migrate at their own pace.
References
- Parent Epic: gitlab-com/gl-infra#1432
- Admin panel setting logging field migration epic: gitlab-org/quality#398
- Related issue: #596493
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.