-
Notifications
You must be signed in to change notification settings - Fork 905
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
Move event-generator #1089
Comments
I would prefer option 2. In that case, I could help! |
/assign |
PoC in progress https://github.com/leogr/event-generator |
As discussed during the community call, we decide to move the new event-generator to the Falco org and - when ready - use it as a replacement for the old one. The new one will live in its own repo. I suggest keeping this issue open until the old one can be removed from this repo. |
+1
Let us know when you are reading for the move!
L.
…On Wed, Apr 8, 2020 at 5:46 PM Leonardo Grasso ***@***.***> wrote:
As discussed during the community call, we decide to move the new
event-generator <https://github.com/leogr/event-generator> to the Falco
org and - when ready - use it as a replacement for the old one
<https://github.com/falcosecurity/falco/tree/master/docker/event-generator>
.
I suggest keeping this issue open until the old one can be removed from
this repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1089 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA5J436YOI4UYRIAHUPGKTRLSL6ZANCNFSM4LGNKOGQ>
.
|
Almost ready for the move 👉 https://github.com/falcosecurity/event-generator/milestone/1 |
Motivation
The event-generator tool is a C++ tool written by @mstemm to generate events Falco can catch.
In the past (example: the PSP generator), we decided to let stay in Falco only what really is Falco.
Which means, that side tooling should live somewhere else.
Furthermore does not seems perfectly fine to me that its source code is inside the
docker
directory.Feature
Discuss in the public (and then act) whether the event-generator tool has to live in Falco or somewhere else.
I see some options:
falcoctl
falcoctl
using the docker image exposing the binary build in case (1)Alternatives
Keep it here.
Additional context
I'll propose a discussion about this in the next community call.
Just talked with @leogr that is available to port it in Go if we all decide like so.
The text was updated successfully, but these errors were encountered: