You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current fabric lifecycle package command relies on positional parameters, so as part of this issue I would like to make improvements as follows...
Package a chaincode
Usage:
fabric lifecycle package <chaincode-path> [flags]
Flags:
-a, --archive string name of the output tgz file
-h, --help help for package
-i, --indexes string path containing state database index definitions for CouchDB
-l, --label string human-readable description of the package
-t, --type string the chaincode type (e.g. GOLANG, JAVA, NODE)
The packaging code currently depends on fabric-sdk-go, however rather than update copies of packaging code from the Fabric peer command in that repo, I would like to either take a more up-to-date cut of the Fabric code, or investigate making use of the fabric-admin-sdk project instead... hyperledger/fabric-admin-sdk#15
The text was updated successfully, but these errors were encountered:
It is possible to create external builders and launchers for Fabric, however there is no easy way to package chaincode for those builders and launchers. For example, Fabric now includes a chaincode as a service builder, and other builders and launchers are available.
The current
fabric lifecycle package
command relies on positional parameters, so as part of this issue I would like to make improvements as follows...The packaging code currently depends on fabric-sdk-go, however rather than update copies of packaging code from the Fabric
peer
command in that repo, I would like to either take a more up-to-date cut of the Fabric code, or investigate making use of the fabric-admin-sdk project instead... hyperledger/fabric-admin-sdk#15The text was updated successfully, but these errors were encountered: