This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Add missing DNSSEC Permissions to "admin-priv-level" Roles #6608
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
ocket8888
added
bug
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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 fixes #6603.
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Create a Role with an "admin" "priv_level", then run the provided migration. Ensure the Role now has the DNS-SEC:READ and DNS-SEC:DELETE Permissions. Then run the "down" migration and ensure they no longer do (although that's probably much less important).
If this is a bugfix, which Traffic Control versions contained the bug?
PR submission checklist