-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
feat: Add configurable AWS KMS encryption context #84
feat: Add configurable AWS KMS encryption context #84
Conversation
ff63278
to
315fcc0
Compare
Thanks for this MR |
1e12dc1
to
56c4802
Compare
1bc7edd
to
00f4aeb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
This is going to need a Bank-Vaults release first and since its version is pinned at the moment, we should probably hold off on merging until a release is done.
ec7b8d9
to
35fc867
Compare
917426b
to
dfe0b2f
Compare
@kirilvasilev would you mind updating the PR? The recent repo changes moved the deployment resources, so this PR is affected. Thanks! |
f4cacaa
dfe0b2f
to
f4cacaa
Compare
Signed-off-by: @kirilvasilev <kiril.v92@gmail.com> Signed-off-by: Kiril Vasilev <kiril.v92@gmail.com>
f4cacaa
to
6cb68cd
Compare
Overview
Features:
This PR is created in order to allow the vault operator to take advantage of this bank-vaults feature
Notes for reviewer
In our use case, we have an existing vault cluster that has existing unseal keys that are encrypted with a custom encryption context. This feature will allow us to migrate this vault cluster to be managed by bank-vaults.