DNS Zones Configuration Update #219
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 atomic configuration reload capability for DNS zones and records.
Key changes:
replace()method for bothDNSStoreandDNSZoneclasses to atomically update configurationsDNSZoneconstructor to accept initial records_is_valid_recordtocheck_recordfor better clarityMappingtype for better zone name uniquenessAll changes covered by comprehensive test suite including edge cases like empty replacements and invalid records.
The main goal is to support safe configuration reloads from external sources (files, databases, etc.) while maintaining data consistency.