-
Volodymyr Paprotski authored
This time use Yaml files in peer and orderer to configure BCCSP factory The main three changes are for the two executables: - peer - orderer - chaincode shim They each have their own config yaml file, added a BCCSP section. The BCCSP is paired with the MSP configuration directory. The SW BCCSP Filestore takes over the keystore directory. Where it gets complicated are all the tests. The tests working against MSP were easy to fix (circa patch set 8) Patch set https://gerrit.hyperledger.org/r/#/c/6235/4 introduced more uses of BCCSP. Configuring those mostly to SW/nil, except need to find an appropriate location for InitFactories(nil). Either: - many/most test cases have function called SetupTestConfig() - TestMain() otherwise Since the TestMain() updates were getting unmanageable and unscalable (everyone writting unit tests would now need to know about InitFactories()), added a concept of bootBCCSP to bccsp/factory. bootBCCSP is meant to be used by test cases that only need keyless crypto operations (i.e. SHA) or where keeping keys does not matter. Change-Id: I084d7927550e7fad7a25cf2062dc20220cf81ccd Signed-off-by: Volodymyr Paprotski <vpaprots@ca.ibm.com>
3ee03339