-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
Chan.Part.API: join system channel using config block IT #2082
Conversation
@@ -968,6 +1096,80 @@ func applicationChannelGenesisBlock(n *nwo.Network, orderers []*nwo.Orderer, p * | |||
return genesisBlock | |||
} | |||
|
|||
func systemChannelGenesisBlock(n *nwo.Network, orderers []*nwo.Orderer, peers []*nwo.Peer, channel string) *common.Block { |
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.
This seems to be duplication of the existing logic for bootstrapping a network. Did you look at simply re-using what's already present via nwo?
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.
The key difference is the flexibility of including different orderers in the consenters set without having a different configtx.yaml (or template). By default, nwo includes all orderers in the consenters set and the endpoints.
Use the configtx library to create the system channel genesis block, as it provides an easy way in tests for explicit control over the orderer endpoints and consenters for a channel. FAB-18273 Signed-off-by: Will Lahti <wtlahti@us.ibm.com>
FAB-18273 Signed-off-by: Will Lahti <wtlahti@us.ibm.com>
These were used previously but not any longer and should be removed. Signed-off-by: Will Lahti <wtlahti@us.ibm.com>
Type of change
Description
First commit:
Second commit:
Third commit:
Related issues
FAB-18273