When a jail use the systemd backend, it does not need a logpath to be set.
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.
<!--
Thank you for contributing to this project!
-->
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
<!--
Thank you for contributing to this project!
-->
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.
-->
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
-->
modulesync 5.4.0
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.
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!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->