-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Support specifying priority on rich rules #296
Conversation
Hi -- will this PR get rolled into a release? Been almost 2 years, but I cannot really convert from firewall to firewalld without the ability to set a priority in rich rules... |
What's the word about getting this approved and implemented? |
@tskirvin there's an open comment from @trevor-vaughan that needs to be addressed :) |
Fair enough, but I'm with @decibelhertz here - I can't really start converting from firewall to firewalld until this is addressed, and I'd prefer to work under the don't-let-perfect-be-the-enemy-of-good policy. |
0e60d59
to
0b48644
Compare
0b48644
to
74f9640
Compare
There we go, must've missed the notification about that comment. Also rebased it onto master while I was at it adding a validation. |
What's the word about getting a new puppet forge release for this change and any others that have come recently? The last official release I see was 4.5.1 back on 15 Aug. |
From what I get this feature is not available in the firewalld version that comes with centOS/rhel 7. So releasing this means the module does not support that OS-version anymore. |
I also find myself needing this enhancement. I thought I might be able to use it by pointing the Puppetfile mod at the github master branch instead of puppetforge, and it does appear that I'm getting code with these changes, but I'm still getting a |
Pull Request (PR) description
Adds support for the
priority
option on rich rules, to allow ordering them outside of the normally implicit - and not guaranteed to be deterministic - ordering imposed by when they're added.