This sample uses fabric-ca to run an end-to-end test similar
to the BYFN sample. However, instead of using cryptogen, it
uses fabric-ca. All private keys are generated dynamically in
the container in which they are used.
This sample also demonstrates how to use abac
(Attribute-Based Access Control) to make access decisions.
See chaincode/abac/abac.go.
Change-Id: I5eddc9e35908e409ac07266c3183ce89a5a6cd82
Signed-off-by: Keith Smith <bksmith@us.ibm.com>
basic-network:
- moved "crypto-config" to top-level and removed
"network" folder
- added generate.sh to re-gen crypto materials
- docker-compose.yaml to ref v1.0.0 images
- add CLI to docker-compose
- start.sh to only start CA, orderer, peer and couch
- startFabric.sh to run start.sh, then launch CLI
for create channel, install, instantiate, invoke
fabcar:
- moved chaincode to central chaincode folder
- moved "creds" to top-level and removed "network"
folder
- changed to use the basic-network as the target
and removed docker-compose.yaml and crypto-config
- updated package.json to require v1.0.0 modules
- added missing license headers
- restructured to use a central chaincode subdirectory
Change-Id: Ic784d1cf55ea51da5155624f3c38275883de1dca
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>
Signed-off-by: Jim Zhang <jzhang@us.ibm.com>
