Add support for defining custom dnssec-policies #206
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
smortex
force-pushed
the
custom-dnssec-policy
branch
from
bd94f89
to
b4fc612
Compare
ekohl
reviewed
Feb 17, 2022
smortex
force-pushed
the
custom-dnssec-policy
branch
from
b4fc612
to
3e58e83
Compare
smortex
force-pushed
the
custom-dnssec-policy
branch
from
51ad705
to
653b75b
Compare
|
I have no strong opinion (and not too versed in dnssec), but it doesn't look crazy to me? ;) |
smortex
force-pushed
the
custom-dnssec-policy
branch
from
653b75b
to
b84ec7f
Compare
|
Thanks! I squashed the commits. |
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.
This is a complement to #205 to allow to setup custom policies.
This is currently a draft until I manage to deploy this code in a real-world workload.