feat: aws secret manager #11
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
shrimalmadhur
force-pushed
the
madhur-elo-369-support-aws-secret-manager-as-storage-option-in-cerberus
branch
from
2e05246 to
566dc8f
Compare
nelsonijih
approved these changes
Nov 21, 2024
nelsonijih
deleted the
madhur-elo-369-support-aws-secret-manager-as-storage-option-in-cerberus
branch
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.
Support AWS secret manager for storing keys
there's another refactor I need to do which will dictate how tests will be written - will do that in subsequent PR.