3e015d6635
Fail2ban's documentation suggests that modifications to the main configuration be done in a .local file instead of modificating the main fail2ban.conf file. If upgrading from a previous version of the module, you will probably end up with both files having the same content. This is pretty harmless, but can be confusing at first. Changes to the fail2ban.local file will have precedence over those in fail2ban.conf so no matter if you previously had a modified fail2ban.conf file, the new values will be used. This change modifies the previous behaviour of the module where the main configuration file was overwritten, but ensures future compatibility with fail2ban.
23 lines
561 B
Puppet
23 lines
561 B
Puppet
# Class: fail2ban::spec
|
|
#
|
|
# This class is used only for rpsec-puppet tests
|
|
# Can be taken as an example on how to do custom classes but should not
|
|
# be modified.
|
|
#
|
|
# == Usage
|
|
#
|
|
# This class is not intended to be used directly.
|
|
# Use it as reference
|
|
#
|
|
class fail2ban::spec inherits fail2ban {
|
|
|
|
# This just a test to override the arguments of an existing resource
|
|
# Note that you can achieve this same result with just:
|
|
# class { "fail2ban": template => "fail2ban/spec.erb" }
|
|
|
|
File['fail2ban.local'] {
|
|
content => template('fail2ban/spec.erb'),
|
|
}
|
|
|
|
}
|