feat: dnssec load keys from AWS Secrets Manager #6618
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
kcolemangt
requested review from
Isolus,
miekg,
chrisohaver,
johnbelamaric,
yongtang and
stp-ip
as code owners
Signed-off-by: kcolemangt <20099734+kcolemangt@users.noreply.github.com>
kcolemangt
force-pushed
the
dnssec-secrets-manager
branch
from
19b8a3e
to
70a33a7
Compare
|
The CI failure in |
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.
1. Why is this pull request needed and what does it do?
Enhancement: Integrate AWS Secrets Manager for DNSSEC Key Management
2. Which issues (if any) are related?
Closes #6616
3. Which documentation changes (if any) need to be made?
Included
4. Does this introduce a backward incompatible change or deprecation?
No