Allow linking any identity from CLI #2187
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
P-77 Allow linking any identity in development
ContextFor easier testing of VC building, we should be able to link any identities (that is, to skip the validation process) in the development. This can be done by calling ✔️ Please set appropriate labels and assignees if applicable. |
kziemianek
approved these changes
Oct 11, 2023
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.
Context
resolves #1816
resolves P-77
This PR enables linking any identity using CLI. It should work under non-prod only.
See the usage example in
link_identity.rs.Please note you still need to set the user shielding key first - it now accepts a DID format instead of plain ss58 string.