Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: mapping of severity UNKNOWN to policy report #1037

Merged
merged 1 commit into from
Jul 20, 2024
Merged

fix: mapping of severity UNKNOWN to policy report #1037

merged 1 commit into from
Jul 20, 2024

Conversation

erikgb
Copy link
Member

@erikgb erikgb commented Jul 20, 2024

After enabling the PolicyReport alpha feature gate in one of our clusters, we observe the following error:

[results[0].severity: Unsupported value: \"\":
 supported values: \"critical\", \"high\", \"low\", \"medium\", \"info\"

The severity field is optional in the PolicyReport API, so I suggest not setting the field if severity is UKNOWN in scan results.

@erikgb erikgb requested a review from a team as a code owner July 20, 2024 12:20
@erikgb erikgb requested a review from tenstad July 20, 2024 12:21
@erikgb erikgb merged commit a5a6b74 into statnett:main Jul 20, 2024
10 checks passed
@statnett-bot statnett-bot bot mentioned this pull request Jul 20, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@tenstad tenstad tenstad approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@erikgb @tenstad