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

Remove invalid reference to dns::server::options::forwarder #121

Merged
merged 1 commit into from May 31, 2015
Merged

Remove invalid reference to dns::server::options::forwarder #121

merged 1 commit into from May 31, 2015

Conversation

darkfoxprime
Copy link

The dns::zone class tried to reference dns::server::options::forwarder as if dns::server::options was a class rather than a defined type. Removing that check for now.

The dns::zone class tried to reference dns::server::options::forwarder as if dns::server::options was a class rather than a defined type.  Removing that check for now.
@darkfoxprime
Copy link
Author

Removing the check against having a global forwarder and a per-zone forwarder until I can figure out how to reference an attribute from a resource defined elsewhere.

@solarkennedy
Copy link
Collaborator

I agree, this is strange and would never work.

Maybe we should give up on dns::server::options being a defined type?

solarkennedy added a commit that referenced this pull request May 31, 2015
…erver-options-forwarder

Remove invalid reference to dns::server::options::forwarder
@solarkennedy solarkennedy merged commit b98f7fd into ajjahn:master May 31, 2015
@darkfoxprime
Copy link
Author

Why is dns::server::options a defined type? Is there ever a reason to use it more than once?

@solarkennedy
Copy link
Collaborator

I personally don't think so. I would merge in a PR to make it not so! :)

@darkfoxprime darkfoxprime deleted the remove-invalid-reference-to-dns-server-options-forwarder branch June 7, 2015 17:31
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