-
Notifications
You must be signed in to change notification settings - Fork 55
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
add datadog user to groups through pillar config #66
Comments
Hey @dmfay, Thanks for the report! That would indeed be useful. It's also something we already do in the other configuration management tools (eg. in ansible-datadog), so it'd be nice to have the same capabilities here too. I'll add a task in our backlog to track this request. |
I would love this as well. Just had to override your init.sls to do this manually. |
Tested on Ubuntu
add
NOTE: we use a gitfs so it might be added in a different place for you. Wherever you import your formulas in put it in there. |
it would be great if this functionality was added by default. Regarding overriding, remember salt filesystems are merged in priority order so if you create a local |
I'm managing several Ubuntu servers in AWS EC2 and want to ship /var/log/auth.log up to Datadog. However, the
dd-agent
user does not have permission to open the file since it does not belong to theadm
group.I can add
dd-agent
to the group on existing servers manually through Salt:But it'd be nice to be able to specify the group membership in the pillar and avoid manual configuration steps (or an extra state across a bunch of minion classes in the topfile), especially as new minions come online.
The text was updated successfully, but these errors were encountered: