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

support applying same sysctl configuration from different puppet classes on the same host #74

Open
sreerajkksd opened this issue Nov 10, 2021 · 1 comment

Comments

@sreerajkksd
Copy link

Right now, name of the sysctl resource is considered as the sysctl key configuration. And there is no additional argument that we can pass to set the sysctl key if we want the name of the file to be different. Of-course, there is an option of using content/source, but that is not what we want most of the time.

I would propose that we add an additional optional argument named $key and default it's value to $title. File names can be created using title, but everything else should rely on $key. This would help us to apply same sysctl configuration on multiple hosts and not bother about the puppet conflicts and sysctl would take care of understanding the ordering of the files.

Any comments ?

@sreerajkksd
Copy link
Author

@thias would you help me reviewing/approving and releasing a new version if I implement this feature ?

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

No branches or pull requests

1 participant