Donate plugins repo to falcosecurity

[leogr]

Description of Request

The following two projects are parts of the libs plugin system proposed by @ldegio:

• https://github.com/leogr/plugins https://github.com/mstemm/plugins this repo will be the place where various plugins will live; currently, it includes four examples
• https://github.com/ldegio/libsinsp-plugin-sdk-go an SDK for implementing plugins in Golang N.B.: we should change the name of this repo (Moved to a separate issue Add plugin-sdk-go repository to falcosecurity organization #101)

This request has to be considered as a dependant of:

• The proposal 👉 docs(proposals): proposal for a libs plugin system falco#1637
• The proposed implementation 👉 wip: plugin system libs#33 https://github.com/falcosecurity/libs/tree/new/plugin-system-api-additions, no PR yet.

Motivation

The plugin system for https://github.com/falcosecurity/libs is a new awesome feature under development.
Basically, this new mechanism will allow plugging new data sources to libscap and libsinsp so that the library's consumers can use them. Thus paving the way to a lot of new possibilities, really. 🥳

When the implementation becomes official, other fundamental pieces will be needed, since:

• plugins need a place and a registry (a unique ID is required for each plugin);
• to facilitate the development of plugins in Golang an SDK is needed (to avoid boilerplates).

Those repositories are WIPs that aims to address the above topics. The repos also reached a point where feedback is needed, and incubating them at some point would help to test-drive implementations.

[fntlnz]

This is a major change on how Falco and the libraries work, we need a proposal for the plugin system first, then we can discuss the incubation for the two repositories once the feature is official. I'm not ok with having the two repositories in before merging the feature.

[leogr]

This is a major change on how Falco and the libraries work, we need a proposal for the plugin system first, then we can discuss the incubation for the two repositories once the feature is official. I'm not ok with having the two repositories in before merging the feature.

I agree with that, so I have updated the description to make that clearer. My initial intention was more about receiving feedback, but it's totally right we first need that the proposal and the implementation get accepted 👍

[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

[mstemm]

We've been moving repos around a little bit while we finished the work, so I created a separate issue to cover just the plugin-sdk-go repository: #101.

Let's let this issue cover the plugins themselves.

I updated the description to note that and updated the repo we'd like to donate to https://github.com/mstemm/plugins.

Please let us know what you think!