Skip to content
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 the dns::zone::slave_masters parameter to be an array #133

Merged
merged 3 commits into from Jul 29, 2015
Merged

Allow the dns::zone::slave_masters parameter to be an array #133

merged 3 commits into from Jul 29, 2015

Conversation

ghost
Copy link

@ghost ghost commented Jul 28, 2015

This just changes the zone.erb template to allow the @slave_masters parameter to be an array, in which case it gets joined by ";" semicolons; if it's not an array, it's interpolated directly, just like the previous behavior.

@ghost
Copy link
Author

ghost commented Jul 28, 2015

note - i am working on adding spec tests to this; please hold :)

@solarkennedy
Copy link
Collaborator

This is good. While we have not been doing this regularly, can you add a docstring to manifests/zone.pp documenting this parameter?

Something like

# == Parameters
#
# [*slave_masters*]
# .....
#

@ghost
Copy link
Author

ghost commented Jul 29, 2015

I'll add in documentation for all the parameters this evening.

@ghost
Copy link
Author

ghost commented Jul 29, 2015

parameters documented

@solarkennedy
Copy link
Collaborator

Whoa! Awesome!!
Thank you!

solarkennedy added a commit that referenced this pull request Jul 29, 2015
…sters

Allow the dns::zone::slave_masters parameter to be an array
@solarkennedy solarkennedy merged commit 30bfbc8 into ajjahn:master Jul 29, 2015
@ajjahn
Copy link
Owner

ajjahn commented Jul 29, 2015

@jearls wins all the points.

@ghost ghost deleted the allow-array-for-dns-zone-slave_masters branch September 30, 2015 00:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants