You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed with the whole community during yesterday's community call, we're going to move out from the main Falco repository its integrations/ directory.
This relates to the more broader discussion about Falco's official artifacts (falcosecurity/falco#1114).
Hi all,
I just opened a PR for this, merely starting from moving the whole integrations/ directory in the root of this project; I think that could be an as good as little starting point, what do you think?
I don't know if alternatively, you'd want to maintain the history of the related integrations' code, because as is the history is overwritten.
I also read the interesting discussion led by @kris-nova about the Falco artifacts and as discussed also in the last call I totally understand the point and agree.
Because of this I'll keep in mind the real scope of Falco in the whole stack when thinking about the benefis that the integrations - i.e. Kubernetes resources, but not only - could bring and to not to force technologies where they shouldn't, especially from the security perspective.
Motivation
As discussed with the whole community during yesterday's community call, we're going to move out from the main Falco repository its
integrations/
directory.This relates to the more broader discussion about Falco's official artifacts (falcosecurity/falco#1114).
Feature
Move here the
integrations/
directory of Falco./assign @maxgio92
Wait for falcosecurity/test-infra#113 to be merged in, thanks! 🥇
The text was updated successfully, but these errors were encountered: