Skip to content
This repository has been archived by the owner on Aug 25, 2023. It is now read-only.

Use custom KMS store implementation instead of Aries storage provider #327

Open
DRK3 opened this issue Aug 18, 2022 · 0 comments
Open

Use custom KMS store implementation instead of Aries storage provider #327

DRK3 opened this issue Aug 18, 2022 · 0 comments
Assignees
@DRK3
Labels
dependencies Pull requests that update a dependency file
Milestone
0.1.9

Comments

@DRK3
Copy link
Collaborator

DRK3 commented Aug 18, 2022 •
edited
Loading

With this change in Aries, a consumer of the Aries KMS interface can now inject in their own storage without being limited by the overall Aries storage interface defined in the spi module. For now, I'm using a wrapper as a bridge solution (the kms.NewAriesProviderWrapper call) to allow the KMS project to continue functioning, but in order to reap the benefits of this new storage design we should create our own implementation.
@rolsonquadras rolsonquadras moved this from Todo to In Progress in TrustBloc Wallet/VCS Aug 19, 2022
@rolsonquadras rolsonquadras added the dependencies Pull requests that update a dependency file label Aug 19, 2022
@rolsonquadras rolsonquadras added this to the 0.1.9 milestone Aug 19, 2022
@DRK3 DRK3 moved this from In Progress to Todo in TrustBloc Wallet/VCS Aug 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DRK3 DRK3

Labels
dependencies Pull requests that update a dependency file
Projects
No open projects
TrustBloc Wallet/VCS
Status: Todo
Milestone
0.1.9
Development

No branches or pull requests
2 participants
@rolsonquadras @DRK3