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

Sharing macros between falco_rules.yaml and falco_rules.local.yaml #3010

Open
cccsss01 opened this issue Jan 12, 2024 · 3 comments
Open

Sharing macros between falco_rules.yaml and falco_rules.local.yaml #3010

cccsss01 opened this issue Jan 12, 2024 · 3 comments
Milestone

Comments

@cccsss01
Copy link

Motivation

Ease of use faster implementation

Feature
Currently in the falco-modern-bpf host deployment model, it doesn't appear that macros are shared between config files, this would be nice very nice.

Alternatives
Manually insert macros into the configs used.

Additional context
Currently if macros being called in falco_rules.local.yaml are not included the service will fail.

@Andreagit97
Copy link
Member

Hi! Thank you for reporting @cccsss01! This is a nice feature, I'm not sure we can do that with the actual implementation, but we can consider the request. This is in some way related to this #2999...

@Andreagit97 Andreagit97 added this to the TBD milestone Jan 16, 2024
@poiana
Copy link

poiana commented Apr 15, 2024

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

@Andreagit97
Copy link
Member

/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants