jamshale

Hmm. I remember seeing that error a long time ago and thought I had fixed it. Possibly an issue with postgres. I'll look into it.

> Remind me why do we need a restart in single-tenant mode, but not in multi-tenant mode? > > And is there any way to eliminate the requirement? > >...

Haven't been able to reproduce that error yet with the demo and postgres. Also, the integration test `ACA-Py Anoncreds Upgrade` was supposed to be testing this. Will try and reproduce...

> > Love the idea of a tutorial for doing this using Alice/Faber. Is that possible/reasonable/helpful? You do need to do something first (populate the storage) and then do an...

@ianco I'll call you on Monday. I can't replicate it still, but not sure I'm using postgres correctly. I will want the morning to figure it out if it is...

I think it works the way you are describing. The controller doesn't have to manage anything. The acapy agents just need to restart after they detect the upgrade completed, like...

Looks like there's a small change in the `link_secret` record's formatting I never noticed. Existing record was saved as json value ```json {"value":{"ms":"71064680940360014629618879654672290185096545699652080871503389385314050854890"}} ``` but in anoncreds it's expecting to...

@ianco This has been updated. There was two issues when upgrading a multitenant holder. 1. Anoncreds expected the link_secret record to be in a slightly different format. The conversion was...

Also added a small response payload to the upgrade endpoint.

> @jamshale there are conflicts, I think because I merged the other PR - #2861 No problem. I thought there might have been more. I'll rebase it in a bit.