Tenant Import Feature #55
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: jamshale <[email protected]>
Signed-off-by: jamshale <[email protected]>
jamshale
force-pushed
the
tenant-import-feature
branch
from
32444b9 to
2edd75d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.