Closed crux-capacitor closed 5 years ago
@crux-capacitor please add a working pillar.example, that way more variables are documented
@aboe76 added pillar-with-views.example. Let me know if anything else should be clarified. Thanks!
Changed to a WIP. Need to do some more testing on zone file creations.
@aboe76 Ready for review / merge.
Woohoo! Thanks. This is my first pull request ever!
@crux-capacitor, @aboe76 it LGTM (indeed nicely done, btw :))
My only suggestion would be if you can squash the commits so we merge the PR.
Hmm, I'm not having much luck with that. Is there an option to squash and merge?
You can do that in your local working dir, with
git rebase -i HEAD~N
where N is the number of commits you want to rebase (ie 13, here?)
Then, git will open you a commit comment window, where you can decide which commit comment remains, which is 'squashed' etc, and the will produce a result commit which you can push.
Hope that helps
Ah yes, I was missing the HEAD~N part. Hopefully I did that right. Thanks!
@crux-capacitor merged it, nice one, and @javierbertoli thanks for review.
During the for-loop in named.conf.local.jinja, I added a check for a new 'file' argument. If set, then use that file, otherwise default to the specified zone name for this view.
This allows you to set up multiple views configured to serve the same zone but specify the zone file to be used so that they can serve different record sets.
An example of this would be internal and external views that both serve the same zone (company.com), but the external view returns public IPs, and the internal view returns private IPs.
I can provide a working pillar.example of this implementation if needed.