Repository navigation
fix(nextdns): preserve profile settings and Tailnet blocklist policy - #24
Merged
Merged
Conversation
bakerboy448
changed the title
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
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.
Summary
Preserve each target profile's NRD setting when syncing security from Main. The existing payload helper was unused, so sync overwrote target values.
Keep Tailnet on HaGeZi Pro plus OISD while other targets follow Main's Normal plus OISD. Diff recognizes this policy and reports an incorrect Tailnet tier.
Four regression tests cover NRD enabled, disabled, and absent; Tailnet isolation; and correct/incorrect tier comparisons. Tests verify Main stays unchanged. Tests and pre-commit pass.
Script(s) affected
Checklist