-
Notifications
You must be signed in to change notification settings - Fork 70
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
Don't set forbidden zone options for zone type 'forward' #142
Don't set forbidden zone options for zone type 'forward' #142
Conversation
|
@antaflos, the Redmine ticket used is for a different project than the one associated with this GitHub repository. Please either:
If changing the ticket number used, remember to update the PR title and the commit message (using This message was auto-generated by Foreman's prprocessor |
When zonetype => forward is set for a dns::zone resource then ignore any forbidden options that might be set as parameters when rendering the named.zone.erb template. Such forbidden options are "file", "masters", "allow-transfer", "allow-query", "notify" and "also_notify". This prevents the module from generating an invalid named configuration (in zones.conf) that would result in named failing to (re)start. Fixes theforemanGH-141
35e6acb
to
0993455
Compare
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.
Should we do these checks in puppet code and hard error when it's passed in? I like hard failures in catalog compilation so you're aware that you're passing in an invalid configuration.
|
In this case I thought it may be easier and more efficient to make the template aware of the zone type and let it "do the right thing" on its own, without failing the catalog compilation. The use case I thought of was this: when most zones are slave zones we can set defaults for the But if you want I can also change the behaviour like you suggested and fail with a hard error if this is the preferable way to go for this module. |
|
Gently bumping this as well :) |
|
Thanks! |
When zonetype => forward is set for a dns::zone resource then ignore any
forbidden options that might be set as parameters when rendering the
named.zone.erb template. Such forbidden options are "file", "masters",
"allow-transfer", "allow-query", "notify" and "also_notify".
This prevents the module from generating an invalid named configuration
(in zones.conf) that would result in named failing to (re)start.
Fixes GH-141