PR to enhance permissions start script to handle different permission models #248
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
# Conflicts: # docker-compose.yml
passionofvc
added a commit
to passionofvc/ibft-raft-3nodes
that referenced
this pull request
Dec 10, 2020
…cript to handle different permission models
passionofvc
added a commit
to passionofvc/istanbul-tools
that referenced
this pull request
Dec 10, 2020
passionofvc
added a commit
to passionofvc/istanbul-tools
that referenced
this pull request
Dec 10, 2020
fixanoid
approved these changes
Jan 13, 2021
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.
Quorum supports 2 permissions models v1 and v2. v1 is the earlier permission model. v2 enhances the permission model with additional apis and processing level validation.
This PR enhances the
start-permission.shto bring up a permissioned quorum network with either v1 or v2 permission model.