Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/0c0046467dd14feeaf4911c4f5a85011

✔️ ansible-galaxy-importer SUCCESS in 4m 47s
✔️ build-ansible-collection SUCCESS in 9m 33s

What is the status of this PR?

I am also at that point.

The system_wide option in this PR reloads not only the modified file but other files as well. Is this functionality truly necessary?

From the ubuntu man page:

--system
Load settings from all system configuration files. Files are read from directories
in the following list in given order from top to bottom. Once a file of a given
filename is loaded, any file of the same name in subsequent directories is ignored.
/run/sysctl.d/.conf
/etc/sysctl.d/.conf
/usr/local/lib/sysctl.d/.conf
/usr/lib/sysctl.d/.conf
/lib/sysctl.d/*.conf
/etc/sysctl.conf

@MubashirUsman
Thank you for the update :)

From the ubuntu man page

As mentioned in the man page you pointed out, --system option changes the basic behavior of the sysctl module, which defines sysctl parameters in a specific file and reflects the values by reloading only that file. I was concerned about that point.
So, I would like to know the specific use cases that require this function.
The typical use case would be to set several parameters in multiple files and then reload all the files with sysctl --system to apply the changes all at once.
However, sysctl module applies one parameter to one file per task. Therefore I simply thought that the typical bulk application mentioned above might be better handled using the shell module or similar. I'd like to hear your thoughts on this.

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/464e5a1f9bdb40b99071cfb1edfd2675

✔️ ansible-galaxy-importer SUCCESS in 5m 29s
✔️ build-ansible-collection SUCCESS in 5m 44s

I needed to reload two files in different directories and had to use the shell module, sysctl --system to make the changes take effect. Using this, the name parameter won't be needed and can be made optional.
I was setting up the Kubernetes cluster when I had to set module parameters and load overlay and br_netfilter kernal modules in different files.

I needed to reload two files in different directories and had to use the shell module, sysctl --system to make the changes take effect. Using this, the name parameter won't be needed and can be made optional. I was setting up the Kubernetes cluster when I had to set module parameters and load overlay and br_netfilter kernal modules in different files.

Same approach here. Was setting up a kubernetes Cluster.

@MubashirUsman @MaKaNu thank you for your valuable feedback :)
This PR changes past behavior, so it cannot be backported to stable-1, but I agree to merge it into the main branch.

@MubashirUsman could you add some integration tests for this change and create a changelog/fragments file?
You can see more details about the changelog:

• Docs: https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs-how-to
• Examples: https://github.com/ansible-collections/ansible.posix/tree/main/changelogs/fragments
• Integration tests: https://github.com/ansible-collections/ansible.posix/tree/main/tests/integration/targets/sysctl

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/ea66f61cf04546dba4c30af11ed24641

✔️ ansible-galaxy-importer SUCCESS in 3m 54s
✔️ build-ansible-collection SUCCESS in 5m 20s

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/ef2d76b50048424da14ff36891cdf6e1

✔️ ansible-galaxy-importer SUCCESS in 4m 45s
✔️ build-ansible-collection SUCCESS in 5m 28s