feat: add container / host event scope to ruleset - #396
Draft
biscout42 wants to merge 1 commit into
Draft
Conversation
biscout42
changed the title
Tacklebox
reviewed
Aug 20, 2026
Tacklebox
left a comment
Tacklebox
left a comment
Contributor
There was a problem hiding this comment.
I'm not sure it makes sense to write rules based on container.id outside of the special case of LXC, since the ids won't be known at the time when the policy is written since they are generated at runtime right? I don't see any technical issues with the PR though.
christos68k
approved these changes
Aug 20, 2026
biscout42
marked this pull request as draft
August 21, 2026 13:30
Contributor
Author
|
I'll update this logic when #395 is done. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The change allows to filter host events vs container events.