-
Notifications
You must be signed in to change notification settings - Fork 41
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 the event-generator to reflect the recent ruleset split (stable, incubating, sandbox) #86
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
/assign |
This has been addressed by #90 |
Likely, the best way to implement this is to add tags to the actions (similarly to rules tags) and implement a feature that allows filtering by tags. cc @FedeDP wdyt? |
I agree, seems like the simplest solution. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
This has been addressed expect for one point:
I will open a separate issue for that. |
@leogr: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Motivation
Because of the Rules Maturity Framework proposal.
Feature
stable
,incubating
,sandbox
stable
ones by defaultAlternatives
No compelling alternatives.
Additional context
I assume we don't want any more of those rules which are now
deprecated
.Tasks
The text was updated successfully, but these errors were encountered: