-
Notifications
You must be signed in to change notification settings - Fork 81
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
Allow Zone file to be created from a template #129
base: master
Are you sure you want to change the base?
Conversation
@@ -50,6 +50,8 @@ def update(&block) | |||
yield file | |||
file.write "send\n" | |||
file.close | |||
#puts File.read(file.path) | |||
|
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.
Could you get rid of this please?
mode => '0644', | ||
replace => ($zone_file_mode == 'managed'), | ||
content => $content, | ||
audit => [ content ], |
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.
You'll need to get rid of the audit parameters on this and the other file resource. They've been removed on master, and that's the source of the merge conflict.
I've been hesitant to add direct control over zone file content to this module. Conventional zone file handling defeats the option to configure a dynamic zone, which is a necessary precondition for using some of the advanced features of the module. This seems appropriately limited in scope, though. Just a couple of minor clean ups and it will be ready to merge. |
Also, do you mind too much if I squash the branch in the merge? |
Yes, sure. It will be a couple of days until I get to your other comments. |
Follow up from #101 to allow for putting in the file as content. If the $content parameter is non-empty use it as first preference.