-
Notifications
You must be signed in to change notification settings - Fork 70
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(rules): adjust output fields wrt new style guide #122
Conversation
d102298
to
8a7bb37
Compare
8a7bb37
to
63ce05a
Compare
63ce05a
to
df6ecce
Compare
df6ecce
to
41076e1
Compare
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Patch changes:
|
Done |
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.
First pass
https://falco.org/docs/rules/style-guide/ Signed-off-by: Melissa Kilby <[email protected]>
ff09fa3
to
434784d
Compare
Co-authored-by: Leonardo Grasso <[email protected]> Signed-off-by: Melissa Kilby <[email protected]>
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Patch changes:
|
e2e1c53
to
ec3b7dd
Compare
Rules files suggestionsfalco_rules.yamlComparing Major changes:
Patch changes:
|
LGTM label has been added. Git tree hash: dcfd1284cdec1a8f78feaed709d0b683c455cbc7
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: incertum, 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 |
https://falco.org/docs/rules/style-guide/
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area rules
Proposed rule maturity level
What this PR does / why we need it:
@leogr please review with falcosecurity/falco-website#1094 and let me know if we agree on these fields? Same for the name to the left of the field, e.g.
cmdline
orcommand
consistently?That's why I kept this PR to the first ~10 rules only.
In addition, how many rules can I update wrt to output in one PR going forward?
Idea would be to first list the fields more specific to the rule and then append the agreed upon standard fields. The reviewer should double check that no critical unique fields were removed in the process.
The cleanup would also involve removing all
proc.pid
fields, I am explaining in falcosecurity/falco-website#1094 why those fields are best kept for customization by adopters. This being said we have yet to improve the UX to support adding output fields generically to each rule for example ... as we discussed in several Falco tickets.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: