-
Notifications
You must be signed in to change notification settings - Fork 146
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
@planetarium/account-aws-kms #2962
Conversation
3f84081
to
ba8209c
Compare
d74378d
to
24b0a1f
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #2962 +/- ##
==========================================
- Coverage 80.58% 80.53% -0.06%
==========================================
Files 330 330
Lines 11774 11774
==========================================
- Hits 9488 9482 -6
- Misses 2286 2292 +6 |
3b8b478
to
ff2b26f
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.
It seems pretty completed and working now, so let's just merge this then preparing new noble/secp256k1 in seperate issue/PR. shall we?
9ffc80d
to
f8a66a9
Compare
Co-authored-by: Hong Minhee <hong.minhee@planetariumhq.com>
Co-authored-by: Hong Minhee <hong.minhee@planetariumhq.com>
Co-authored-by: Hong Minhee <hong.minhee@planetariumhq.com>
f8a66a9
to
fda1414
Compare
This PR has Quantification details
Why proper sizing of changes matters
Optimal pull request sizes drive a better predictable PR flow as they strike a
What can I do to optimize my changes
How to interpret the change counts in git diff output
Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email) |
This PR introduces
@planetarium/account-aws-kms
, which providesAwsKmsAccount
andAwsKmsKeyStore
that uses AWS KMS as backend.Also, it fixes the case where
Signature
in@planetarium/account
accepts a high-S signature.