Jakub Dzikowski
Jakub Dzikowski
To reproduce: create a config with two chaincodes with the same name (on different channels). The network won't start, since we do not aim (yet?) to support chaincodes with the...
Any sample could be used like this one for example https://github.com/hyperledger/fabric-samples/tree/main/asset-transfer-basic/chaincode-go
It should probably use JSON Schema extentions
See: https://hyperledger-fabric.readthedocs.io/en/latest/create_channel/create_channel_participation.html
``` #!/bin/sh peer="peer1.org1.com" channel="my-channel2" chaincode="chaincode1" command='{"Args":["KVContract:get", "name"]}' docker exec "cli.org1.com" peer chaincode invoke \ --peerAddresses "$peer:7051" \ --tlsRootCertFiles "/var/hyperledger/cli/crypto/peers/peer1.org1.com/tls/ca.crt" \ -C "$channel" \ -n "$chaincode" \ -c "$command" \ --waitForEvent...
Introduce or improve commands to manage network lifecycle, for example: - [ ] install new chaincode (it should install it in the network and update Fablo config file) - [...
Probably this is a good case to use Yeoman (prompt for chaincode language or forward to dedicated generator). Proposed API: ``` ./fabrica init => prompt ./fabrica init java => create...