Skip to content
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(policymatcher): skip future matching in case block/audit matches #1855

Merged
merged 1 commit into from
Sep 3, 2024

Conversation

daemon1024
Copy link
Member

@daemon1024 daemon1024 commented Aug 26, 2024

Purpose of PR?:

Fixes #1692

Does this PR introduce a breaking change?
NA

If the changes in this PR are manually verified, list down the scenarios covered::
Tested against policy mentioned in bug report

Checklist:

  • Bug fix. Fixes #
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

Copy link
Collaborator

@Prateeknandle Prateeknandle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why are we not skipping when matched for allow case?

any specific reason?

@Aryan-sharma11 Aryan-sharma11 merged commit 8525ec6 into kubearmor:main Sep 3, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Policy name is not matching in the logs; instead, we see it as Defaultposture
3 participants