This file is used to list changes made in each version of the iptables-ng cookbook.
- Remove deprecated foodcritic linting
- Apply cookstyle linting fixes
- Enable unified_mode
- Rewrite tests to Inspec, remove deprecated minitest
- Remove logic for EOL distros
- Update kitchen test platforms
- Support Github Actions for integration tests
- Add support for Chef-13
NOTE: If you want to continue using iptables-ng
on Chef 12, version lock this cookbook to 3.0.1
. This can be achieved by putting the following in your Berksfile
:
cookbook 'iptables-ng', '~> 3.0.1'
- Fix issue with resource cloning in Chef 13
Release to workaround cloning issues, for the upcoming Chef-13 release:
- Removed the feature to automatically run
iptables-ng::install
upon LWRP usage. It's now required to manually runiptables-ng::install
before using the LWRPs. This can be achieved by adding the following before using the LWRPs for the first time (also make sure it's only included once):
include_recipe 'iptables-ng::install'
- Removed the feature to automatically create new custom chains when using the
iptables_ng_rule
provider. Custom chains are now required to be added manually before using them:
iptables_ng_chain 'CUSTOM'
iptables_ng_rule 'rule-using-custom-chain'
This release also fixes a bug previously introduced by trying to workaround the cloning issues, where a chain policy wasn't properly updated. See this issue for details.
- Add compatibility fix for older chef-clients
- Add workarounds for duplicate resource warnings
- Add compatibility setting for
source_url
attribute inmetadata.rb
- Revert
use_inline_resources
, was causing trouble
- Fix code linting complaints (rubocop, foodcritc)
- Add
use_inline_resources
to providers
- Add
node['iptables-ng']['auto_prune_attribute_rules']
attribute to remove unused/ old rules created by attributes automatically
- Add support for Debian Jessie
- Add possibility to disable the reload or restore of iptables at the end of a chef run
- Only install
iptables
package on Amazon Linux
- Check whether name attribute in rule provider is valid
- Fix an issue with resource notification in rule provider
- Fix an issue with nat table on ipv6 not properly skipped on systems without ip6tables nat support
- Add
node['iptables-ng']['ip6tables_nat_support']
attribute, default to true on recent Ubuntu versions
- Add posibility to add an "action" when configuring iptables rules via attributes. See README for details
- Fix an issue with init-script name on Ubuntu >= 14.10 (was renamed to netfilter-persistent)
- Add support for RHEL 7 compatible distributions
- Add support for
node['iptables-ng']['enabled_tables']
- Fix an issue with
node['iptables-ng']['enabled_ip_versions']
, Thanks Bob Ziuchkovski - Add Travis with rubocup and foodcritic checks
- Add rubocup
- Add attribute
node['iptables-ng']['enabled_ip_versions']
- Support custom chains
- Rename/Migrate iptables_ng_policy provider to iptables_ng_chain
- Fixes duplicate resource name warnings [CHEF-3694], Thanks James FitzGibbon
-
Support for ip_version parameter in attributes. See README for details.
If you use attributes to configure iptables_ng, you need to migrate
node['iptables-ng']['rules']['filter']['INPUT']['rej'] = 'myrule'
to
node['iptables-ng']['rules']['filter']['INPUT']['rej']['rule'] = 'myrule'
- [Chris Aumann] - Initial release of iptables-ng