Unify Security Configuration between EE and CE
What does this MR do and why?
The Security Configuration page needs to show different information depending on the tier the given project is in. Currently, the logic of that behavior is scattered in various places on the frontend and backend, which makes adding features or moving features to different tiers difficult and error-prone. read more in the issue description
In this MR we add a response for the CE version of SecurityConfigurationController
for json
request, so it returns configuration data. This change is behind the feature flag. It's needed until frontend is adjusted as well
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
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.
Related to #339023 (closed)