-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allow configuration of OSQuery #3
Comments
Also asked in kbrebanov/ansible-osquery#2 |
Sounds like a plan. I'm not interested in separate configs per platform, though, so let's try to make it a minimum viable config. |
I would likely replicate the existing one? https://github.com/ssummer3/ansible-osquery/blob/master/files/etc/osquery/osquery.conf Can then be overridden by the playbook variables as required (presumably we'll know the OS at that point from the inventory). Smth like:
|
Hmm. This might not need doing. I wonder if I'll test this. |
I think OSQuery uses JSON to configure it's behaviour. Would you be happy getting a PR that allowed configuring it by specifying its full configuration tree in yaml, and using the toJson filter of Ansible to render it to it's final format?
I think this is more flexible and lower overhead than allowing a set of specific configuration option
The text was updated successfully, but these errors were encountered: