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

cleanup plugins rules files #1995

Merged
merged 5 commits into from
May 12, 2022
Merged

cleanup plugins rules files #1995

merged 5 commits into from
May 12, 2022

Conversation

leogr
Copy link
Member

@leogr leogr commented May 9, 2022

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #1994

Special notes for your reviewer:

Ruleset files were already moved to the plugins repository by falcosecurity/plugins#98

/milestone 0.32.0

Does this PR introduce a user-facing change?:

update!: moving out plugins ruleset files

leogr added 3 commits May 9, 2022 13:18
…3707942ab52219e98f461

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Plugins' rules files now lives in their repositories. See falcosecurity/plugins#98

Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
leogr and others added 2 commits May 9, 2022 16:49
Signed-off-by: Leonardo Grasso <me@leonardograsso.com>
Signed-off-by: Jason Dellaluce <jasondellaluce@gmail.com>
@jasondellaluce jasondellaluce force-pushed the cleanup/plugins-rules-files branch from 4190f17 to d6a5cc9 Compare May 9, 2022 16:55
@jasondellaluce
Copy link
Contributor

Hey @leogr, this is a great thing. I feel like plugin rulesets are better suite to be in the plugins repository and distributed separately, thanks for making the first step in this direction. Since I was the CI failing, I pushed an additional commit in this branch to fix-up the regression tests related to k8s audit!

@FedeDP FedeDP mentioned this pull request May 10, 2022
53 tasks
@leogr leogr changed the title wip: cleanup plugins rules files cleanup plugins rules files May 12, 2022
Copy link
Contributor

@jasondellaluce jasondellaluce left a comment

Choose a reason for hiding this comment

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

/approve

@poiana
Copy link
Contributor

poiana commented May 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jasondellaluce, leogr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:
  • OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana poiana merged commit 96e2864 into master May 12, 2022
@poiana poiana deleted the cleanup/plugins-rules-files branch May 12, 2022 16:28
@jasondellaluce jasondellaluce added this to the 0.32.0 milestone May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Move plugins' rulesets close to plugins
4 participants