-
Notifications
You must be signed in to change notification settings - Fork 739
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
What is the uscase of sysctl_overwrite over ansible.posix.sysctl? #683
Comments
To actually st the sysctl-parameters, we already use
I agree here. I'd love to have a better implementation where you can set default parameters, operating-system-specific parameters and user-provided variables. If you have an idea, please let me know. |
Closing, feel free to reopen if you need further info. |
Hi @rndmh3ro, Thanks for the explanation. |
No worries! :) |
Hi,
can you explain that's the usecase or when to use sysctl_overwrite?
Especially as there is ansible.posix.sysctl (https://docs.ansible.com/ansible/latest/collections/ansible/posix/sysctl_module.html).
We have the problem, that we need to define different settings in sysctl in different groups, with overlapping settings, which makes it a little bit error prone and hard to manage. We may need to witch to ansible.posix.sysctl, but I was curious why sysctl_overwrite was implemented originally?
Thank You.
The text was updated successfully, but these errors were encountered: