Add support for unmanaged zone contents for externally-managed zones #151
Conversation
This file contains hidden or 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
optiz0r
force-pushed
the
unmanaged_zone_contents
branch
from
db02bb4 to
b3c8421
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds
bind::zone::manage_contentsparameter which defaults to true. When set to false, the content of the zone file is not managed by puppet. This allows the module to co-exist with external tooling which manages the zone file contents, while still using this module to manage configuration of the zone. When manage_zone is set false for non-master zones, zone files are no longer removed from disk where this module thinks them not relevant.Readme is updated with a usage example.