Draft: Enable the maven request forward by default
🍸 Context
The maven request forward is a feature that allows requests to the Package Registry to be forwarded.
More precisely, if a Maven package is not found in the GitLab maven package registry, the request is forwarded to the official registry (https://search.maven.org/).
This feature is controlled by a group setting that is powered by the cascading setting part.
Given that the Maven Repository is one of the most used registries on gitlab.com, the related application setting has been set to false
there.
In addition, we used a feature flag to deploy this change. The rollout issue is: #359553+.
The feature flag has been enabled globally on gitlab.com for <code data-sourcepos="13:70-13:70">X</code> days without any issue.
With this MR, we are enabling the feature flag by default and adjusting the documentation. An feature flag enabled by default provides an additional safety net (we can disable the change globally or for specific root groups).
🤔 What does this MR do and why?
- Enable
maven_central_request_forwarding
by default. - Update the related documentation.
📺 Screenshots or screen recordings
See
⚙ How to set up and validate locally
See
🏍 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.