-
Notifications
You must be signed in to change notification settings - Fork 902
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.
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
update(userspace/engine): improve skip-if-unknown-filter YAML field #2749
Conversation
Signed-off-by: Jason Dellaluce <[email protected]>
Signed-off-by: Jason Dellaluce <[email protected]>
/milestone 0.36.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: 993dbe6a5e746d9509c3a0a4eb1841ba46dd8499
|
Requires falcosecurity/testing#22 to be merged to have tests passing. |
Signed-off-by: Jason Dellaluce <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
LGTM label has been added. Git tree hash: e221a43ee07dfc44cd5e0b11d1163c4e6ef010c7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: FedeDP, jasondellaluce, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind bug
/kind feature
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
The
skip-if-unknown-filter
YAML field can be used in Falco rules for skipping a rules if it fails compilation due to an unknown filter field. This PR proposes enlarging its scope to also missing fields in rules' outputs (a bug, currently), and also checking for unknown event types (which can occur more frequently, now that plugins can define new value ofevt.type
with async events). The idea is forskip-if-unknown-filter
to skip rules if "there's something unknown in a rule's filter", with the output being included for parity as it uses the same fields available for rules' filters.A follow-up PR adding tests is falcosecurity/testing#22.
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: