Support min_version
and max_version
on evaluation primitives and RASP operator versioning
#343
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.
This PR introduces:
min_version
andmax_version
tags on evaluation primitives (rules, exclusion filters, processors and scanners). These tags are used define the range oflibddwaf
versions[min_version, max_version]
for which the rule should be applied. When the evaluation primitive is not compatible with the current version, the ID is included in the relevant diagnostics, within the newskipped
section.sqli_detector@v2
. The current implementation only allows a single version number, rather than the typical three dot-separated version numbers. Operator version numbers work as follows: