github.com/lzy4123/fabric@v2.1.1+incompatible/internal/peer/lifecycle/chaincode/testdata/connectionprofile-bad.yaml (about)

     1  name: connection-profile-bad
     2  
     3  #
     4  # Any properties with an "x-" prefix will be treated as application-specific, exactly like how naming
     5  # in HTTP headers or swagger properties work. The SDK will simply ignore these fields and leave
     6  # them for the applications to process. This is a mechanism for different components of an application
     7  # to exchange information that are not part of the standard schema described below. In particular,
     8  # the "x-type" property with the "hlfv1" value example below is used by Hyperledger Composer to
     9  # determine the type of Fabric networks (v0.6 vs. v1.0) it needs to work with.
    10  #
    11  x-type: "hlfv1"
    12  x-loggingLevel: info
    13  
    14  #
    15  # Describe what the target network is/does.
    16  #
    17  description: "The network to be in if you want to stay in the global trade business"
    18  
    19  #
    20  # Schema version of the content. Used by the SDK to apply the corresponding parsing rules.
    21  #
    22  version: 1.2.0
    23  
    24  #
    25  # [Optional]. But most apps would have this section so that channel objects can be constructed
    26  # based on the content below. If an app is creating channels, then it likely will not need this
    27  # section.
    28  #
    29  channels:
    30    # name of the channel
    31    mychannel:
    32      # Required. list of orderers designated by the application to use for transactions on this
    33      # channel. This list can be a result of access control ("org1" can only access "ordererA"), or
    34      # operational decisions to share loads from applications among the orderers.  The values must
    35      # be "names" of orgs defined under "organizations/peers"
    36      orderers:
    37        - orderer.example.com
    38  
    39      # Required. list of peers from participating orgs
    40      peers:
    41        peer0.org1.example.com:
    42          # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
    43          # have the chaincode installed. The app can also use this property to decide which peers
    44          # to send the chaincode install request. Default: true
    45          endorsingPeer: trueish
    46  
    47          # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
    48          # installed. The app can also use this property to decide which peers to send the
    49          # chaincode install request. Default: true
    50          chaincodeQuery: occasionally
    51  
    52          # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
    53          # queryBlock(), queryTransaction(), etc. Default: true
    54          ledgerQuery: notachance
    55  
    56          # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
    57          # produce events but the app typically only needs to connect to one to listen to events.
    58          # Default: true
    59          eventSource: true
    60  
    61        peer0.org2.example.com:
    62          # [Optional]. will this peer be sent transaction proposals for endorsement? The peer must
    63          # have the chaincode installed. The app can also use this property to decide which peers
    64          # to send the chaincode install request. Default: true
    65          endorsingPeer: true
    66  
    67          # [Optional]. will this peer be sent query proposals? The peer must have the chaincode
    68          # installed. The app can also use this property to decide which peers to send the
    69          # chaincode install request. Default: true
    70          chaincodeQuery: true
    71  
    72          # [Optional]. will this peer be sent query proposals that do not require chaincodes, like
    73          # queryBlock(), queryTransaction(), etc. Default: true
    74          ledgerQuery: true
    75  
    76          # [Optional]. will this peer be the target of the SDK's listener registration? All peers can
    77          # produce events but the app typically only needs to connect to one to listen to events.
    78          # Default: true
    79          eventSource: true