Update Vulnerability Summary counts for filtering by `cluster` and `image` filters
Why are we doing this work
- the summary counts on the vulnerability report should be updated when filtering by
cluster
andimage
filters
Relevant links
Non-functional requirements
-
Documentation: -
Testing:
Implementation plan
-
backend modify Project.vulnerabilitySeveritiesCount
to be used withclusterAgentId
andimage
-
frontend modify vulnerability_severities_count.query.graphql to take clusterAgentId
andimage
(see diffs below)
diff --git a/ee/app/assets/javascripts/security_dashboard/graphql/queries/vulnerability_severities_count.query.graphql b/ee/app/assets/javascripts/security_dashboard/graphql/queries/vulnerability_severities_count.query.graphql
index 47338b4be30..1de441b7fd3 100644
--- a/ee/app/assets/javascripts/security_dashboard/graphql/queries/vulnerability_severities_count.query.graphql
+++ b/ee/app/assets/javascripts/security_dashboard/graphql/queries/vulnerability_severities_count.query.graphql
@@ -10,6 +10,8 @@ query vulnerabilitySeveritiesCount(
$scannerId: [VulnerabilitiesScannerID!]
$hasIssues: Boolean
$hasResolution: Boolean
+ $clusterAgentId: [ClustersAgentID!]
+ $image: [String!]
$isGroup: Boolean = false
$isProject: Boolean = false
$isInstance: Boolean = false
@@ -53,6 +55,8 @@ query vulnerabilitySeveritiesCount(
scannerId: $scannerId
hasIssues: $hasIssues
hasResolution: $hasResolution
+ clusterAgentId: $clusterAgentId
+ image: $image
) {
...VulnerabilitySeveritiesCount
}
Verification steps
- Ensure your GDK has a GitLab Ultimate license
- Ensure your GDK is connected to the GitLab Runner
- Follow these docs to set up the kubernetes agent
- Clone test-cis-with-agentid and run the pipeline
- Link the agent to a project
- Run the pipeline to generate vulnerabilities
- Navigate to the project/group/security center vulnerability report
- View the vulnerabilities
Edited by Alexander Turinske