Compliance Framework Report feature flag and folder preparation
What does this MR do and why?
Initial setup work for the new compliance Framework Report.
Create development feature flag compliance_frameworks_report, and wire it up to render a new top-level component (reports_app.vue - currently empty). If disabled, render the existing report as normal so no user facing changes are visible.
This new top level component will eventually have tabs to allow switching between different reports.
In preparation for adding additional reports in here, I've moved all of the current violations report code into a violations_report subdirectory. In the next MR, I will add a new frameworks_report subdirectory for the new report, and a shared folder to extract common components into.
Screenshots or screen recordings
| FF disabled | FF enabled |
|---|---|
 |
 |
How to set up and validate locally
- Browse to a Group -> Security & Compliance -> Compliance Report
- There should be no visible changes when feature flag is disabled
- There should be a blank new page when feature flag is enabled
Feature.enable(:compliance_frameworks_report)
Feature.disable(:compliance_frameworks_report)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 #387910 (closed)