This repository has been archived by the owner on Apr 18, 2023. It is now read-only.
feat: make ssm peer id and private key optional #15
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
v-stickykeys
approved these changes
Apr 22, 2022
smrz2001
deleted the
feature/plat-511-make-ssm-peer-idprivate-key-optional-in
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The current version of this module does not allow reusing existing IPFS peer IDs and private keys. As a result, any IPFS nodes created using the module will start with a clean slate and that partners who wish to reuse their existing IPFS identities will not be able to do so.
The updates in this PR add support for using SSM to provide existing IPFS identities, if configured during the application of the module.