Flush rules for INPUT chain only (for compatibility with docker) #106
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request refactors the firewall playbook to introduce the ability to flush only the INPUT chains, while leaving other chains (such as DOCKER chains) untouched. This change is made to ensure compatibility with Docker configurations.
The following changes have been made:
firewall_flush_rules_input_nat
: Indicates whether to flush the INPUT chain in the 'nat' table.firewall_flush_rules_input_mangle
: Indicates whether to flush the INPUT chain in the 'mangle' table.firewall_flush_rules_input_filter
: Indicates whether to flush the INPUT chain in the 'filter' table.These changes ensure compatibility with Docker configurations and provide more flexibility in managing firewall rules.