Draft: Create vulnerabilities route/page for instance
What does this MR do?
Create vulnerabilities route/page for instance
- similar to how groups/dashboard and groups/vulnerabilities is separated, now there is a security/dashboard and security/vulnerabilities
- separate instance security charts and vulns
- move the instance-level vulnerabilities into a separate page
- show the charts by default
- remove charts from the vulnerability page
- add tests
Screenshots
Before | After - Page 1 | After - Page 2 |
---|---|---|
NOTE: Yes, the breadcrumbs are not styled properly on either .com
or in this fix, but I am going to fix that in a separate MR to not have it bogged down by this MR
How to reproduce
https://gitlab.com/snippets/1956676
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #230412 (closed)
Edited by Alexander Turinske