Federico Di Pierro

> I've tried adding the kernel headers and build environment. The folder the error complains about does exist: Note that it complains about the `build` folder: `/lib/modules/6.1.32-v8+/build` and i don't...

/milestone 0.38.0

> This would require the aforementioned change to the current behavior, plus the need to avoid triggering an exception when an included file is missing (since the default Falco config...

WDYT @falcosecurity/falco-maintainers ? I'd love to gather some feedback around this, this might be a good time since we are just past the 0.37.0 release.

> Could we include the new "includes" key in the falco.yaml with a description Yes! I'd love to do that in a follow up PR, where i also split up...

> What if I pass includes over the cmd options -o, should be all fine right? We only support scalar values for the `-o` override. See https://github.com/falcosecurity/falco/blob/master/userspace/falco/configuration.cpp#L613 EDIT: i was...

> In addition, would it be possible to allow an empty includes: Added a test; it was already working fine. > Plus could we not allow self referencing the original...

> Does it get an error or silently fail? Silently fail. I think it must be documented in a follow-up PR (ie: when i split main Falco config into different...

We can add a warning perhaps?

Implemented.