-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
feat: AWS kms signer support for forc-client #6578
Conversation
Looks like we hit a flaky test (hopefully, as it was not failing in previous commit and now it is failing): #5376 (comment) |
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 Kaya mostly looks good. Just wondering if you can first add doc comments to all public types and functions before we merge this.
Is this entirely additive or does it include breaking behavior? |
This is entirely additive, |
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.
Apart from "is is", it's good to go
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.
utACK
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.
Approving for now but it would be good to address Sophie's feedback in a follow up PR.
## Description ~~waiting on #6578~~ This release contains no API changes and along with bug fixes, upgrades support for fuel-core to 0.36 and fuels SDK to 0.66.5.
Description
closes #6560.
closes #6559.
This PR adds AWS kms signer support. Which is enabled if
--aws-kms-signer <ARN>
is present. If that is the case, an aws client is created which is used to create a AwsSigner.With this PR, we are able to supply a signing arn and with that we can sign a transaction. This enables being able to revoke signing authority for aws kms managed keys. So we can control deployments and owner/target changes for a proxy contract. Effectively enabling multi-sig like proxy contracts via aws kms.