-
Notifications
You must be signed in to change notification settings - Fork 912
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
Cleanup list fields #1816
Cleanup list fields #1816
Conversation
eae9afa
to
0c0ab65
Compare
0c0ab65
to
f2c8e68
Compare
Instead of having a falco-specific function to print field info, use the built-in filter_fieldclass_info::as_string() instead. This is a better implementation (displays addl info, has better wrapping, wider output) and having a single implementation allows for consistent outputs between falco and other potential programs that could use the libs. Signed-off-by: Mark Stemm <[email protected]>
With the new implementation of list_fields(), the order of fields changed slightly. So update the checksum. Signed-off-by: Mark Stemm <[email protected]>
Update json_event_filter_factory::get_fields() to add the new info (shortdesc, data_type, tags) to field descriptions. This allows for richer outputs when printing info on the fields. Signed-off-by: Mark Stemm <[email protected]>
This has required changes to print info on fields. Signed-off-by: Mark Stemm <[email protected]>
f2c8e68
to
aa7e3e1
Compare
/milestone 0.31.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
For more context, this is built on top of the changes of falcosecurity/libs#153 and aligns Falco to them.
LGTM label has been added. Git tree hash: 045b1387804ffac6b3a56bd337982e42204bc43d
|
/milestone 0.31.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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leogr, mstemm 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?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: