Open
Conversation
Member
|
|
|
Hi @bsnyder788, sorry for the delay. We've been figuring out how we wanted to enable this feature internally and started discussing your design here and how we have rolled it out. I dropped the ball on closing the loop. I'm getting the details on our implementation and will provide a review early next week. |
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
3 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 adds the ability to enable the enterprise encryption at rest feature. It supports providing a secret name where the store
encryption key (and the previous one if applicable) is located.
Checklist
[ X] I have added these changes to the changelog (or it's not applicable).