-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the Indy SDK to Askar Migration process #2340
Document the Indy SDK to Askar Migration process #2340
Conversation
Signed-off-by: Stephen Curran <[email protected]>
Let me know what you think of this as a migration document. It covers both the why and the how -- borrowing heavily from the blog post type article that Alex created, and the process that @WadeBarnes uses in migrating BC Gov instances. Suggestions welcome! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good other than the broken links to [aries-acapy-tools]
.
If you have an existing deployment, in changing the `--wallet-type` | ||
configuration setting, your database must be migrated from the Indy SDK format | ||
to Aries Askar format. In order to facilitate the migration, an Indy SDK to | ||
Askar migration script has been published in the [aries-acapy-tools] repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Broken link to [aries-acapy-tools]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks — fixed.
Signed-off-by: Stephen Curran <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Signed-off-by: Stephen Curran [email protected]