Update the event-generator to reflect the recent ruleset split (stable, incubating, sandbox)

[leogr]

Motivation

Because of the Rules Maturity Framework proposal.

Feature

• Reflect rules' changes
• Implement a way to select action groups stable, incubating, sandbox
• Only enable stable ones by default

Alternatives

No compelling alternatives.

Additional context

I assume we don't want any more of those rules which are now deprecated.

Tasks

Beta Give feedback

1. Update for Falco 0.37 - event-generator 0.11 #90
   approved area/commands area/events area/pkg dco-signoff: yes kind/cleanup kind/documentation kind/feature lgtm size/XL +10
   

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[leogr]

/assign

[leogr]

• Only enable stable ones by default

This has been addressed by #90

[leogr]

• Implement a way to select action groups stable, incubating, sandbox

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?

[FedeDP]

I agree, seems like the simplest solution.

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale
cc @alacuku @GLVSKiriti