Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for AWSKMS #415

Closed
wants to merge 6 commits into from
Closed

Conversation

MVrachev
Copy link
Member

Fixes #344

Add support for AWSKMS and do small refactorings.

Signed-off-by: Martin Vrachev [email protected]

We don't need to access the keyvault to get the currently used signer
and from it to receive the public key dict, so that we can create
a new SSLibKey...
The reason we don't need to do that is because the public key we pass to
the keyvault is the same key we actually want to add to targets and is
from the correct type.
There is no need to go through all that work just to retreat a
SSLibKey.

Signed-off-by: Martin Vrachev <[email protected]>
This check is already covered in the "else" statement.

Signed-off-by: Martin Vrachev <[email protected]>
Signed-off-by: Martin Vrachev <[email protected]>
@MVrachev MVrachev requested a review from kairoaraujo October 19, 2023 09:47
@lukpueh
Copy link
Collaborator

lukpueh commented Dec 4, 2023

@MVrachev, I suggest we work out #427 first. If we do it right, we should get AWSSigner for free. :)

@MVrachev
Copy link
Member Author

This pr is superseded by a new pr #452 using a different concept.
Closing.

@MVrachev MVrachev closed this Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Task: Implement Key Vault for AWS KMS
2 participants