80 lines
3.6 KiB
YAML
80 lines
3.6 KiB
YAML
name: connection-profile-bad
|
|
|
|
#
|
|
# Any properties with an "x-" prefix will be treated as application-specific, exactly like how naming
|
|
# in HTTP headers or swagger properties work. The SDK will simply ignore these fields and leave
|
|
# them for the applications to process. This is a mechanism for different components of an application
|
|
# to exchange information that are not part of the standard schema described below. In particular,
|
|
# the "x-type" property with the "hlfv1" value example below is used by Hyperledger Composer to
|
|
# determine the type of Fabric networks (v0.6 vs. v1.0) it needs to work with.
|
|
#
|
|
x-type: "hlfv1"
|
|
x-loggingLevel: info
|
|
|
|
#
|
|
# Describe what the target network is/does.
|
|
#
|
|
description: "The network to be in if you want to stay in the global trade business"
|
|
|
|
#
|
|
# Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
|
|
#
|
|
version: 1.2.0
|
|
|
|
#
|
|
# [Optional]. But most apps would have this section so that channel objects can be constructed
|
|
# based on the content below. If an app is creating channels, then it likely will not need this
|
|
# section.
|
|
#
|
|
channels:
|
|
# name of the channel
|
|
mychannel:
|
|
# Required. list of orderers designated by the application to use for transactions on this
|
|
# channel. This list can be a result of access control ("org1" can only access "ordererA"), or
|
|
# operational decisions to share loads from applications among the orderers. The values must
|
|
# be "names" of orgs defined under "organizations/peers"
|
|
orderers:
|
|
- orderer.example.com
|
|
|
|
# Required. list of peers from participating orgs
|
|
peers:
|
|
peer0.org1.example.com:
|
|
# [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
|
|
# have the chaincode installed. The app can also use this property to decide which peers
|
|
# to send the chaincode install request. Default: true
|
|
endorsingPeer: trueish
|
|
|
|
# [Optional]. will this peer be sent query proposals? The peer must have the chaincode
|
|
# installed. The app can also use this property to decide which peers to send the
|
|
# chaincode install request. Default: true
|
|
chaincodeQuery: occasionally
|
|
|
|
# [Optional]. will this peer be sent query proposals that do not require chaincodes, like
|
|
# queryBlock(), queryTransaction(), etc. Default: true
|
|
ledgerQuery: notachance
|
|
|
|
# [Optional]. will this peer be the target of the SDK's listener registration? All peers can
|
|
# produce events but the app typically only needs to connect to one to listen to events.
|
|
# Default: true
|
|
eventSource: true
|
|
|
|
peer0.org2.example.com:
|
|
# [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
|
|
# have the chaincode installed. The app can also use this property to decide which peers
|
|
# to send the chaincode install request. Default: true
|
|
endorsingPeer: true
|
|
|
|
# [Optional]. will this peer be sent query proposals? The peer must have the chaincode
|
|
# installed. The app can also use this property to decide which peers to send the
|
|
# chaincode install request. Default: true
|
|
chaincodeQuery: true
|
|
|
|
# [Optional]. will this peer be sent query proposals that do not require chaincodes, like
|
|
# queryBlock(), queryTransaction(), etc. Default: true
|
|
ledgerQuery: true
|
|
|
|
# [Optional]. will this peer be the target of the SDK's listener registration? All peers can
|
|
# produce events but the app typically only needs to connect to one to listen to events.
|
|
# Default: true
|
|
eventSource: true
|