-
Notifications
You must be signed in to change notification settings - Fork 8.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
FAB-23 user given name instead of fabric generated hash
FAB-23 is implemented by this changeset. Deployment usage change : name has to be specified in addition to path. For example in the sample below, "-n mycc" will serve as the name of the chaincode. peer chaincode deploy -n mycc -p github.com/hyperledger/fabric/ examples/chaincode/go/chaincode_example02 -c '{"Args":["init","a", "100","b","200"]}' The name should be unique. The Life Cycle System Chaincode (LCCC) maps unique chaincode names to other chaincode properies such as Version and deployment spec using chaincode state variables. With these we no longer need to depend upon generated hash to provide uniqueness. We may still use hash to restrict duplicate deployments of the same code but using different names in a separate story. Also we will disallow some characters in chaincode name for use in future support for namespaces. Currently these characters are "/[]{}$:". Unit tests have been modified to use name. In particular, example04 no longer needs to depend on generated hash and uses user provided name. Change-Id: I6b81f75e54cb13aa19b9c9d982b3756c5dca7440 Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>
- Loading branch information
Srinivasan Muralidharan
committed
Nov 4, 2016
1 parent
351423d
commit c3a3e2f
Showing
17 changed files
with
120 additions
and
76 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.