-
Notifications
You must be signed in to change notification settings - Fork 112
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
Add support for views #35
Comments
A drawback of the namespace idea would be that the number of views would be limited to the difference between the concat priority of the header content and the footer content. We could make it a large number, but it would still be a caveat. |
You can do this by using include statement of bind:
/etc/bind/view1:
/etc/bind/view2:
|
Closed
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I really want to implement views, but after hacking at it for awhile, I'm not entirely sure how to implement this. The problem is that zones need to be nested inside the view in which they belong. There's a one-to-many relationship between views and zones, and the puppet language doesn't give us a good way implement this relationship. I've just started toying with the idea of implementing this by creating a namespace for the concat priority. An example would be the view having a concat priority of 1000, but using an inline template to make the concat priority of the zones inside that view be 1001. I'm really not sure what this would look like...I'm going to have to flesh it out some more. Any ideas?
The text was updated successfully, but these errors were encountered: