Skip to content

[FEAT] vulnerability artifacts in the CI should not be filtered #809

@cjdcordeiro

Description

@cjdcordeiro

Describe the solution you'd like

We intentionally filter out Pebble, vulnerabilities <HIGH,CRITICAL, and whatever CVEs are in .trivyignore. However, this is our passing rule, and not really what the CI should spit out as the vulnerability assessment.

GOAL: keep the current logic, but make sure to also scan the rocks without any filters, uploading the corresponding report as the CI artifact

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions