Skip to content

Commit 91da2a0

Browse files
author
Srinivasan Muralidharan
committed
FAB-1665 go chaincode does not need core.yaml
https://jira.hyperledger.org/browse/FAB-1665 All parameters are passed to chaincode via environment variables or as parameters. Default properties are not picked up from core.yaml. In 1.0 architecture, the peer no longer builds the chaincode package but only passes it to docker to deploy (the package is built by CLI or SDK). In this mode the core.yaml in the Dockerfile will typically not be available in the peer environment. Change-Id: Ifffece4edb4fda103c379b644327972429034a2b Signed-off-by: Srinivasan Muralidharan <[email protected]>
1 parent ad02d0c commit 91da2a0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

core/chaincode/platforms/golang/package.go

+1-1
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ func writeChaincodePackage(spec *pb.ChaincodeSpec, tw *tar.Writer) error {
6161
}
6262

6363
//let the executable's name be chaincode ID's name
64-
newRunLine := fmt.Sprintf("RUN go install %s && cp src/github.com/hyperledger/fabric/peer/core.yaml $GOPATH/bin && mv $GOPATH/bin/%s $GOPATH/bin/%s", urlLocation, chaincodeGoName, spec.ChaincodeID.Name)
64+
newRunLine := fmt.Sprintf("RUN go install %s && mv $GOPATH/bin/%s $GOPATH/bin/%s", urlLocation, chaincodeGoName, spec.ChaincodeID.Name)
6565

6666
//NOTE-this could have been abstracted away so we could use it for all platforms in a common manner
6767
//However, it would still be docker specific. Hence any such abstraction has to be done in a manner that

0 commit comments

Comments
 (0)