Closed hwhesselink closed 4 years ago
Best reviewed: commit by commit
Powered by Pull Assistant. Last update 8acb4cc ... 557287b. Read the comment docs.
Thanks for the PR, @hwhesselink -- apologies for the delayed response. Let see if we can get any reviews from previous contributors.
@n-rodriguez You've contributed to this formula before, would you be able to have a quick look at this PR to see all is OK?
If not, perhaps we can find some other method to ensure this formula is maintained.
@myii sorry for the delayed answer. Actually I don't use shorewall anymore (I use ufw) so I'm not sure I'm the right person to review this PR. Maybe @daks still using it?
Nope, I don't use it anymore, using straight iptables now.
@hwhesselink Do you have a plan for further PRs? If so, I might consider adding all of the standardised structure and CI to make things easier to review, etc. Otherwise, perhaps we can just merge this as-is.
@myii The core Shorewall developer stepped down last year https://sourceforge.net/p/shorewall/mailman/message/36589783/ and it appears to be in maintenance mode, so I doubt I'll be submitting further (major) PRs. Given that the kernel seems to be moving away from iptables I don't expect anyone else to pick up development. So maybe just merge as-is and I'll fix issues if they arise.
@hwhesselink Thanks for the patience -- merged. Thanks to all others for their feedback, as well.
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
Update the formula to handle version 5:
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context