GitHub puppet-fail2ban
This module installs, configures and manages the Fail2ban service.

Repo Checks ( 22 of 26 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Debian
No translation
passed
Supports Latest Debian
No translation
passed
Supports Only Current Ubuntu
No translation
passed
Supports Latest Ubuntu
No translation
failed
Supports Only Current Opensuse
No translation
passed
Supports Latest Opensuse
No translation
failed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
passed
Supports Only Current Almalinux
No translation
passed
Supports Latest Almalinux
No translation
passed
Supports Only Current Rocky
No translation
passed
Supports Latest Rocky
No translation
passed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
failed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
failed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

`logpath` is not required when `journalmatch` in provided
bug

When a jail use the systemd backend, it does not need a logpath to be set.

Open PR in GitHub
Add·banaction_allports·parameter·for·supported·versions

Pull Request (PR) description

Added $banaction_allports parameter to support changing banaction_allports.

Note that some spaces have been removed from modified template files due to the root EditorConfig trim_trailing_whitespace setting.

Open PR in GitHub
WIP: Add support for package install options
needs-tests
enhancement

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Add support for package install options.
See puppet package resource for more info:
https://puppet.com/docs/puppet/7/types/package.html#package-attribute-install_options

Open PR in GitHub
Allow changing the ports of the fail2banned services
merge-conflicts
needs-work

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

This request allows changing the default port for any service watched by fail2ban. Check Readme.md for the usage of the "ports" parameter.

Most changes made in this request are just ternary operators on templates and the addition of the "ports" parameter hash to init.pp

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

Adds feature: Allow modification of default ports for each service

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub
modulesync 5.4.0
modulesync

modulesync 5.4.0

Open PR in GitHub
Support overriding configuration for default jails
merge-conflicts

The PR addresses the same issue as #48 but with a bit more generic approach.

Using 2 level Hash might be possible to override basically any attribute in the template.

yaml
fail2ban::jails:
- ssh
- ssh-ddos
fail2ban::jails_config:
ssh:
port: 'ssh,2200'
ssh-ddos:
port: 'ssh,2200'

Using lookup() in templates might not be the best approach, but I can't think of better alternative. Passing explicitly each variable explicitly to the template would generate loads of code. Another option is to write a custom function for checking key existence in the configuration hash (but it doesn't add much to code readability).

Let me know if you're ok with this, so that I'm able to proceed with modifying rest of jails.

Open PR in GitHub
Beaker acceptance test : add idempotency check

This PR also:
* add some rework because fail2ban::config and fail2ban::service are privates
* drop unused files
* rename spec file accordingly with tested class

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Open PR in GitHub