Move a standalone agent from an arbitrary location into a multi-tenant multi-wallet agent.
Only works for multi-tenant, multi-wallet agents
Copies the standalone database to the location next to the admin wallet and then creates the wallet records and forward route mappings for the connection and did keys.
Should allow all the configs available through the api when creating a sub wallet to be declared from the command line.
Adds raw key support to this tool and the existing tools.
Tests it fairly well with automated testing, but only with postgres. sqlite is quite complicated for restarting agents. Creates an admin agent and a standalone on 2 different instances and volumes. Creates connection and a credentials flow through issuance and revocation. Runs the migration and then reruns the same flow with the existing connection.
Potential problems:
Is there possibly keys that need a foward route I don't know about and haven't tested?
passwords and security during migrations
Adds a couple other, not important features to the existing tools.
Move a standalone agent from an arbitrary location into a multi-tenant multi-wallet agent.
Only works for multi-tenant, multi-wallet agents
Copies the standalone database to the location next to the admin wallet and then creates the wallet records and forward route mappings for the connection and did keys.
Should allow all the configs available through the api when creating a sub wallet to be declared from the command line.
Adds raw key support to this tool and the existing tools.
Tests it fairly well with automated testing, but only with postgres. sqlite is quite complicated for restarting agents. Creates an admin agent and a standalone on 2 different instances and volumes. Creates connection and a credentials flow through issuance and revocation. Runs the migration and then reruns the same flow with the existing connection.
Potential problems:
Adds a couple other, not important features to the existing tools.