-
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
fix(userspace/engine): make sure exception fields are not optional in replace mode #3108
Conversation
This PR may bring feature or behavior changes in the Falco engine and may require the engine version to be bumped. Please double check userspace/engine/falco_engine_version.h file. See versioning for FALCO_ENGINE_VERSION. /hold |
Could you please add a test for this behavior? This way we won't break it in the future. |
/milestone 0.38.0 |
… replace mode Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
fc63582
to
8de17fb
Compare
Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
LGTM label has been added. Git tree hash: 201862dc1d9651dcafa33c7ea163dfd7a6e4fdf3
|
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: FedeDP, jasondellaluce, LucaGuerra 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 |
/unhold |
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
When replaced with the new
override
YAML construct,exceptions
must not have any of their sub-fields as optional, just like when first defined in regular rules definitions.Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: