de20b44101
Prior to this commit, the deprecated `manage_redhat_firewall` param was not actually backward compatible because there were several cases where we couldn't tell the difference between the user explicitly specifying `false` for that parameter as opposed to not specifying it at all. This commit is a bit ugly because it sets some defaults to `undef` in order to allow us to tell the difference between the two cases, but it should resolve backwards compatibility issues. |
||
---|---|---|
.. | ||
database_ini.pp | ||
firewall.pp | ||
jetty_ini.pp | ||
validate_db.pp |