Skip to content

[FE] Add export button for framework report

What does this MR do and why?

Implements #387912 (closed)

Adds UI to trigger framework export

Note:

  1. This is will currently not show, since the backend needs to push the path for the button to be visible. This has been done so the feature only shows once the backend part is shipped. (pseudo feature guard)

  2. Export compliance framework report - backend (#388686 - closed) • Sam Figueroa, Jay Montal • 16.0 • On track needs to be merged first for this to be able to trigger an export.

documentation will be added later as this doesn't enable the feature to show yet.

Screenshots or screen recordings

Screenshot_2023-05-02_at_22.29.19

How to set up and validate locally

Apply this diff to make the export button show.

diff --git a/ee/app/views/groups/security/compliance_dashboards/show.html.haml b/ee/app/views/groups/security/compliance_dashboards/show.html.haml
index 798d683dfc04..0ac4b7e6381a 100644
--- a/ee/app/views/groups/security/compliance_dashboards/show.html.haml
+++ b/ee/app/views/groups/security/compliance_dashboards/show.html.haml
@@ -2,6 +2,7 @@
 - page_title _("Compliance report")
 
 #js-compliance-report{ data: {
+  frameworks_csv_export_path: 'foobar/test/path.csv',
   merge_commits_csv_export_path: group_security_merge_commit_reports_path(@group),
   group_path: @group.full_path,
   root_ancestor_path: @group.root_ancestor.full_path,
(END)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Sam Figueroa

Merge request reports

Loading