-
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
update: bump Falco engine version to 7 #1381
Conversation
Signed-off-by: Leonardo Grasso <[email protected]>
2b16191
to
f384dac
Compare
LGTM label has been added. Git tree hash: e936bbc26da0bbdeb6738802e31f8b18b74c5518
|
@@ -16,7 +16,7 @@ limitations under the License. | |||
|
|||
// The version of rules/filter fields/etc supported by this falco | |||
// engine. | |||
#define FALCO_ENGINE_VERSION (6) | |||
#define FALCO_ENGINE_VERSION (7) |
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 see that FALCO_FIELDS_CHECKSUM was already updated with the new checksum, great. Generally, whenever that checksum changes, the engine version needs to change too.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fntlnz, 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 bug
/kind feature
Any specific area of the project related to this PR?
/area engine
/area rules
What this PR does / why we need it:
This PR bumps the engine version to the expected number (7), as per https://falco.org/docs/rules/#versioning
Furthermore, it also sets the
required_engine_version
to 7 in the rule files, to show the expected error when the ruleset does not match. Unfortunately, this must be set to the entire rule files (even though it's required just by few rules) since therequired_engine_version
does not work on rule level (thus the PR #1273 is blocked)./milestone 0.26.0
Which issue(s) this PR fixes:
Fixes #1380
Fixes #1272
Special notes for your reviewer:
I'd propose closing the #1273 in favor of this since the current implementation does not support
required_engine_version
at rule level.An alternative of setting the
required_engine_version
to 7 for the whole file is to create a rules file for every version depending on what are the supported fields, as initially proposed in this comment. If we got consensus for this alternative, I will open another PR (since the main purpose of this PR is just to bump the engine version number and not to fix the whole problem).Finally, this PR intentionally does not try to solve the other problem reported by #1277
/cc @fntlnz
/cc @leodido
/cc @mstemm
Does this PR introduce a user-facing change?: