Remove frontend code for security_auto_fix with functionalities

changed milestone to %16.11

added Deliverable backend devopssecure feature flag frontend groupcomposition analysis maintenanceremoval sectionsec typemaintenance workflowin dev labels

assigned to @zmartins

	1 Warning
	This merge request contains lines with testid selectors. Please ensure `e2e:package-and-test` job is run.

`testid` selectors

The following changed lines in this MR contain testid selectors:

`ee/app/assets/javascripts/security_dashboard/components/shared/project_pipeline_status.vue`

-      <div v-if="autoFixMrsCount" class="gl-md-ml-3" data-testid="auto-fix-mrs-link">

If the e2e:package-and-test job in the qa stage has run automatically, please ensure the tests are passing. If the job has not run, please start the trigger-omnibus-and-follow-up-e2e job in the qa stage and ensure the tests in follow-up-e2e:package-and-test-ee pipeline are passing.

For the list of known failures please refer to the latest pipeline triage issue.

If your changes are under a feature flag, please check our Testing with feature flags documentation for instructions.

Reviewer roulette

Category	Reviewer	Maintainer
frontend	`@andrei.zubov` (UTC+1, same timezone as author)	`@vitallium` (UTC+1, same timezone as author)

Please check reviewer's status!

Reviewer is available!
Reviewer is unavailable!

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

afca084c - Remove frontend code for security_auto_fix with

Compare with previous version

Bundle size analysis [beta]

This compares changes in bundle size for entry points between the commits 6ece5c34 and f4d3dd12

Special assets

Entrypoint / Name	Size before	Size after	Diff	Diff in percent
average	4.24 MB	4.24 MB	-	-0.0 %
mainChunk	3.22 MB	3.22 MB	-	0.0 %

Note: We do not have exact data for 6ece5c34. So we have used data from: 5b95c8f5.
The intended commit has no webpack pipeline, so we chose the last commit with one before it.

Please look at the full report for more details

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for f4d3dd12

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Monitor     | 4      | 0      | 0       | 0     | 4     | ✅     |
| Govern      | 3      | 0      | 0       | 0     | 3     | ✅     |
| Plan        | 4      | 0      | 0       | 0     | 4     | ✅     |
| Create      | 8      | 0      | 3       | 0     | 11    | ✅     |
| Data Stores | 2      | 0      | 0       | 0     | 2     | ✅     |
| Package     | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 21     | 0      | 4       | 0     | 25    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-review-qa: test report for f4d3dd12

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 8      | 0      | 3       | 0     | 11    | ✅     |
| Package     | 0      | 0      | 1       | 0     | 1     | ➖     |
| Govern      | 3      | 0      | 0       | 0     | 3     | ✅     |
| Monitor     | 4      | 0      | 0       | 0     | 4     | ✅     |
| Data Stores | 2      | 0      | 0       | 0     | 2     | ✅     |
| Plan        | 3      | 0      | 1       | 0     | 4     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 20     | 0      | 5       | 0     | 25    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

@ekigbo Would you perform the maintainer review ?

requested review from @ekigbo

approved this merge request

resolved all threads

enabled an automatic merge when the pipeline for 1dc643d8 succeeds

merged

@ekigbo, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:

Ensure the merge request is not in Draft status.
Start a pipeline (especially important for Community contribution merge requests).
Set the merge request to auto-merge.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.