Support other KMS providers (e.g. AWS)
Open
@chasefleming is already working on this.
Since Mar 30, 2023.
Feature
Feedback
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
Issue To Be Solved
Currently the Flow CLI only supports Google KMS.
Example:
...
"accounts": {
"admin-account": {
"address": "service",
"key": {
"type": "google-kms",
"index": 0,
"signatureAlgorithm": "ECDSA_P256",
"hashAlgorithm": "SHA3_256",
"resourceID": "projects/flow/locations/us/keyRings/foo/bar/cryptoKeyVersions/1"
}
}
}
...
You can also use a key management system (KMS) to sign the transactions. Currently, we only support Google KMS.
(Optional): Suggest A Solution
Add support for other KMS providers (e.g. aws-kms, azure-kms, etc), or provide sample on docs that shows workaround for other KMS providers if functionality already exists.
(Optional): Context
Requested on Discord
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.