Remove remaining use of "Severity Class" in where_levels_auto #1311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What:
A remaining use of "Severity Class" in where_levels_auto has been
removed.
Why:
The function generating SQL for the special "levels" keyword was still
using the setting and the old version of severity_in_level with three
parameters, which have been removed.
How:
With a new gvmd database, getting a report caused an error because of the now removed version of the SQL function
severity_in_level
with three parameters. With the changes applied this should work again.Checklist: