This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
Unifying template sets into one (bind9_authoritative now supports strict value)
#8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ulvida
force-pushed
the
feature-issue5
branch
4 times, most recently
from
d84a739 to
5f9d1c8
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR codes #5 proposed features, continuing what was achieved in #6 (ca1c663).
We managed to put together a single set of unified templates that covers all the required configuration customizations, incorporating the improvements of the new set of templates
strict_authoritative/to the default one.Now, setting
bind9_authoritative:strictwe can configure a strict authoritative nameserver. Ifbind9_authoritativeis in a different value the role maintains its default behavior.