-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use custom_jails parameter #100
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this is considered breaking but this does improve things IMHO.
if $config_custom_jails { | ||
create_resources('fail2ban::jail', $config_custom_jails) | ||
} | ||
create_resources('fail2ban::jail', $::fail2ban::custom_jails) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't the leading ::
on a variable considered bad practice?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bad practice is overstating it IMHO. They are needed in Puppet 3 to match Puppet 4+ behavior without them. With it's always absolute. Given the rest of the module is still using the absolute version I'd prefer consistency over the modern way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is a breaking change for any user calling the module like this :
class { 'fail2ban' :
custom_jails => undef,
...
}
With this PR it is impossible to use undef
value.
Fixes issue #99