-
-
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
Service filename bugfix #266
Service filename bugfix #266
Conversation
cb2d810
to
0e73b50
Compare
Dear @trevor-vaughan, thanks for the PR! This is pccibot, your friendly Vox Pupuli GitHub Bot. I noticed that your pull request contains merge conflict. Can you please rebase? You can find my sourcecode at voxpupuli/vox-pupuli-tasks |
0e73b50
to
26ec34f
Compare
26ec34f
to
52327e2
Compare
This started out as a fix for the custom service filename but spiraled a bit further during debugging. * Auto-correct the filename for firewalld::custom_service * Add a function `firewalld::safe_filename` for munging filenames to safely work with firewalld. The allowed characters were determined by experimentation and are not documented. * Ensure that firewalld_zone resources automatically reload the firewall * Ensure that firewalld_zone names are no longer than 17 characters per the manual * Create firewalld::reload and firewalld::reload::complete classes to allow easier resource chaining * Fix spacing in init.pp * Ensure that all of the Execs that call firewall-cmd happen after the service is running * Ensure that all permanent configuration changes happen before the firewalld service is started/restarted. This is critical if switching from nft to iptables due to the segfault bug in nft * Ensure that all custom service declarations happen before all firewalld_zone resources are triggered. This is automatic in all native types * Updated the service.xml.erb to an EPP file Closes voxpupuli#265
52327e2
to
c3020fd
Compare
7883463
to
1be2c90
Compare
@bastelfreak Could have sworn that I fixed all of those the first time :-| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me, but i cannot really tell if its backwards incompatible or not
@bastelfreak The API was not changed and the entire test suite that we have in simp/iptables did not have to be modified at all with these changes. |
This started out as a fix for the custom service filename but spiraled a
bit further during debugging.
firewalld::safe_filename
for munging filenames tosafely work with firewalld. The allowed characters were determined by
experimentation and are not documented.
the manual
allow easier resource chaining
service is running
firewalld service is started/restarted. This is critical if switching
from nft to iptables due to the segfault bug in nft
firewalld_zone resources are triggered. This is automatic in all
native types
Closes #265
Pull Request (PR) description
This Pull Request (PR) fixes the following issues