feat(userspace/engine): update libs ref and adapt to transformer AST changes#3799
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 |
f9e0562 to
1f57ca0
Compare
1f57ca0 to
097e28f
Compare
c2574be to
7cc57f4
Compare
149614b to
3ebecdd
Compare
|
LGTM label has been added. DetailsGit tree hash: f4a12fc27a81c974c66cd3b81bca9617b3ca81dc |
leogr
left a comment
There was a problem hiding this comment.
Hey @irozzo-1A
Thanks for this.
I believe skip-if-unknown-filter is missing from the rule JSON schema (rule_json_schema.h), which contributes to 2 of the 4 failures. That's a pre-existing gap we should fix.
The other failures suggest behavioral changes in how filters are compiled and evaluated with the new libs. See my comment below.
3ebecdd to
0913d62
Compare
…changes - Bump default falcosecurity/libs to latest main (8f6b914) with transformer_list_expr and field_transformer_expr (values) support - Add visit(transformer_list_expr*) to filter_details_resolver and filter_macro_resolver visitors - Fix field_transformer_expr handling to use e->values instead of e->value Signed-off-by: irozzo-1A <iacopo@sysdig.com>
Signed-off-by: irozzo-1A <iacopo@sysdig.com>
After PR falcosecurity/libs#2776 a new error message has been introduced for unknown types. Signed-off-by: irozzo-1A <iacopo@sysdig.com>
0913d62 to
8153c44
Compare
|
LGTM label has been added. DetailsGit tree hash: ee64030c486f608612c3a31ee79b4d4c84c1c755 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ekoops, irozzo-1A, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/unhold |
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area engine
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?: