Fix emitting non-exact out selectors. #801
Merged
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.
out-selectors
enable a hierarchical logic to receive and emit messages. If an agent list listens tov3.report
then he will receive all messages likev3.report
,v3.report.vulnerability
,v3.report.xxx
.If an agent states
out-selector
, he should in the same fashion be able to emit all sub-messages.The current implementation was doing an exact match:
Fix switch to
startswith
check: