GitHub puppet-ipset
Puppet module to manage ipset tooling and actual sets

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Debian
No translation
Supports Latest Debian
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

modulesync 4.0.0

modulesync 4.0.0

Avoid emptying set file for unmanaged sets

(#39) This change applies the inverse of the ignore_content
variable to the replace parameter on *.set file resources in the
ipset::set class, preventing unmanaged ipsets from having their set
files emptied each puppet run

Thank you for contributing to this project!


Pull Request (PR) description

Per the ipset::unmanaged section in the readme, unmanaged sets won't be kept if the set options are changed, but the set file is still emptied with each puppet run. It does leave the in-memory set in place, but this is less than ideal as in the event of an unexpected reboot the set could remain empty until the set file is next updated.

This change leaves the set file intact in addition to the in-memory ipset for unmanaged sets. This is more inline with my expectation of how an unmanaged set should behave, but I'm curious what you think.

This Pull Request (PR) fixes the following issues