bcgov / orgbook-configurations

Build and Deployment Configurations for the Indy-Catalyst version of the OrgBook
Apache License 2.0
3 stars 11 forks source link

Upgrade Orgbook dev configuration to use Aries Askar storage #128

Open swcurran opened 1 year ago

swcurran commented 1 year ago

Preliminary tests are positive, so we should plan on moving OrgBook Dev to Askar.

WadeBarnes commented 1 year ago

When you say preliminary tests are positive, are you referring to testing being performed by @ianco?

swcurran commented 1 year ago

Yes.

ianco commented 1 year ago

FYI I'm still testing. The migration itself looks good but I lose the wallet when I restart the services. I think it's an issue with the aries-vcr docker stuff but I'm still looking into it ...

swcurran commented 1 year ago

OK — I was putting this in as something we need to do sometime relatively soon. I’m sure we (or the CWU cohort) will figure out what’s happening.

ianco commented 1 year ago

I've also added an issue to include some kind of progress indicator, because you don't get any kind of feedback as it's converting the credentials, and with our orgbook wallets this step is going to take "awhile"

ianco commented 1 year ago

OK done testing, all looks good.

I created an issue to add more verbose logging during the conversion - https://github.com/hyperledger/aries-acapy-wallet-upgrade/issues/9