-
Notifications
You must be signed in to change notification settings - Fork 905
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: bump libs and adapt Falco to new libsinsp event source management #2507
Conversation
…d713c6375c Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
/milestone 0.35.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.
LGTM thanks!
LGTM label has been added. Git tree hash: cf10039ecc4d223526961a0e837601c2f5440d2e
|
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
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Andreagit97, FedeDP, incertum, jasondellaluce 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 cleanup
Any specific area of the project related to this PR?
/area build
/area engine
What this PR does / why we need it:
This syncs Falco with the latest libs, and adapts the event source management logic to match the one of libsinsp. Moreover, we now make sure that the plugin loading order is preserved as in the Falco configuration. This allows for an optimal and more predictable event source management. Also, more explicit errors are thrown when events with unexpected event source are fetched during a capture (both live and offline).
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: