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

option to test falco rules before applying #194

Closed
juju4 opened this issue Jan 22, 2017 · 4 comments · Fixed by #286
Closed

option to test falco rules before applying #194

juju4 opened this issue Jan 22, 2017 · 4 comments · Fixed by #286

Comments

@juju4
Copy link
Contributor

juju4 commented Jan 22, 2017

To test configuration, you can use 'falco -c %s -L'.
ansible has a validate option to test a new file before replacing old one. it works fine for falco.yaml but not to falco_rules.yaml.

it would be nice if 'falco -c %s -L' could also apply to rules file alone or have another option to do so.
it allows play to gracefully fail when there is an error in rules.

it also means you can update falco.yaml, validate, update falco rules and at next play falco.yaml validation will fail because of rules file.

Thanks

@mstemm
Copy link
Contributor

mstemm commented Jan 24, 2017

Sounds like a great idea, I'll make sure it happens in the next falco release.

@mstemm
Copy link
Contributor

mstemm commented Feb 15, 2017

I just tried and falco -L does validate the contents of the rules file in addition to the configuration file. This is a somewhat recent change, in 0.5.0, as a part of #150 and #151.

So I think that should be sufficient. If you're looking for the ability to only validate falco_rules.yaml go ahead and reopen and I'll add that ability.

@mstemm mstemm closed this as completed Feb 15, 2017
@juju4
Copy link
Contributor Author

juju4 commented Feb 16, 2017

yes, it's more the latter: only validate falco_rules.yaml
it doesn't seem that I can reopen myself.

@mstemm
Copy link
Contributor

mstemm commented Feb 16, 2017

Ah ok, I'll reopen then.

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

Successfully merging a pull request may close this issue.

2 participants