tracee-rules: Allow compiling and evaluating all Rego signatures at once #1015
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This patch adds new implementation of types.Signature that compiles all Rego signatures into one Rego policy, which is then evaluated with input events. This implementation is more efficient in terms of number of memory allocations and number of objects created to evaluate a Rego policy. The new implementation is activated by specifying the --rego-aio flag. Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>
simar7
reviewed
Sep 20, 2021
Signed-off-by: Simar <simar@linux.com>
simar7
reviewed
Sep 20, 2021
simar7
reviewed
Sep 20, 2021
simar7
approved these changes
Sep 20, 2021
Signed-off-by: Daniel Pacak <pacak.daniel@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds new implementation of types.Signature that compiles
all Rego signatures into one Rego policy, which is then evaluated
with input events. This implementation is more efficient in terms
of number of memory allocations and number of objects created to
evaluate a Rego policy.
The new implementation is activated by specifying the --rego-aio
flag.
Signed-off-by: Daniel Pacak pacak.daniel@gmail.com