-
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
Allow append of new exceptions to rules #1780
Conversation
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.
Before reviewing... Why the commit comes from a GitHub user that sign-offs commit with @mstemm email?
The DCO (implemented via the sign-off) requires the contributor's email (not another one) AFAIK |
6a91bef
to
e338ced
Compare
@leodido I had wrongly infered that sign-off needs to be one of the owner. I corrected the commit message. |
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.
Just the one error return that should also have context and warnings.
@sai-arigeli I was not understanding because looking at your fork/other PRs via the GitHub events I saw that you were signing-off correctly there (sysdig or gmail email)... |
Closing and reopening to trigger the CI |
@leogr: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@leogr: Reopened this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/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.
I thought of another change--since this changes the behavior of how falco reads rules files, you should bump the falco engine version here: /~https://github.com/falcosecurity/falco/blob/master/userspace/engine/falco_engine_version.h#L19. Can you increment it to 11?
826bbcd
to
c9096f8
Compare
@mstemm Fixed this! |
Hey @sai-arigeli as per our policy, merge commits are not allowed. Could you use |
38870fb
to
9a273e2
Compare
9a273e2
to
5ba8d8d
Compare
Signed-off-by: Sai Arigeli <saiharisharigeli@gmail.com> Return warnings after validation of rule exceptions Signed-off-by: Sai Arigeli <saiharisharigeli@gmail.com> Update FALCO_ENGINE_VERSION Signed-off-by: Sai Arigeli <saiharisharigeli@gmail.com>
5ba8d8d
to
34cebff
Compare
LGTM label has been added. Git tree hash: 492d3631bcbc013216e768f3f89f738cff4d3e1e
|
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leogr, sai-arigeli 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 feature
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
PR introduces appending of new fully valid exception objects to existing rules.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: