using the simpleCollectionStore in transactionContext,
get the policy and evaluate it against the signedData to
decide whether a private data access should be allowed or not.

FAB-13039 #done

Change-Id: I9f66ae70aac5c439ec5dc943407c59d365ef5d84
Signed-off-by: senthil <cendhu@gmail.com>

Let the tool do what it wants with the imports.

Change-Id: I115230369be6349d89b5869951ce088ce38d8fb6
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: I5107d00794faf1f41befaff9bb45f6ee3dbd668b
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Make sure that a chaincode can invoke the new metadata-related getters and
setters only if the channel operates in 1.2 mode.

Change-Id: I15e77cd88a6e7ef0e802b02743a7e3cbdcc30ee3
Signed-off-by: Alessandro Sorniotti <ale.linux@sopit.net>
Signed-off-by: Matthias Neugschwandtner <eug@zurich.ibm.com>

The PackageProvider presently returns a chaincode deployment spec.
However, this is far more information than the chaincode runtime
launcher actually needs, as it already knows the chaincode version, type
etc.  So, this CR adds a small method to the cc fs provider to return
only the package bytes and not the rest of the cds and removes the
associated complexity from the chaincode runtime launcher and tests.

Change-Id: Id5ed31ed1fa5030bbb530c55e7c65f6f9a8eccc2
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

The container runtime currently takes both a cccid and a deployment
spec.  And pulls some information from each.  Instead, it should take a
structure which contains exactly the information it needs.

Change-Id: I6c421a0f943aecef481be0b8b6ad6b3a7f5c4b0c
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

This is step two to remove lifecycle from the chaincode package,
replacing the explicit dependency in the tests on the lifecycle
implementation with a mocked implementation.

Change-Id: I4243d691d2de7dabac3af998c3b8b8354e80a602
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

Because of some errors with cyclical imports for the chaincode package
tests which are not written as _test packages, we need to define a
structure to represent a chaincode which is not the
ChaincodeDeploymentSpec but which is also not inside of the chaincode
package.  Defining this in the lifecycle portion makes sense, so as a
prerequisite, moving lifecycle from the chaincode package, to a
subpackage called lifecycle.

Note: This introduces some stuttering, that will be remedied in a later
CR.

Change-Id: I8883b9fc39d7b23d42ba6df31389e5a9df248457
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

HandleInvokeChaincode should have returned the pb.ChaincodeMessage from
the target handler as the response payload but it was returning the
payload from the response. The handler now returns the original message.

The TestChaincodeInvokeChaincode test has also been restored and is no
longer skipped by default.

Change-Id: I42aeb8504d70dd9435f55050cb7f0da3f71c8977
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Icffce261c676fd80afecfeafbc873288c950ffca
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Registry holds LaunchState to track launching instead of a bare channel.
When launches complete, the embedded channel is closed. The error
managed by LaunchState can be used to determine if the launch failed or
succeeded.

Change-Id: Ib069c5752915a8839cf9af50ab94224345e4ffc3
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: I17627eea18627b0c62ff8b20a5642c933075f85b
Signed-off-by: Saad Karim <skarim@us.ibm.com>
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

- Remove constructor in favor of explicit dependency injection from
  ChaincodeSupport to the handler instance.
- Add some documentation comments and group fields in Handler
- Change state to int based enum so zero value matches default state of
  created
- Rename getCCRootName to chaincodeName to more accurately reflect what
  is returned

Change-Id: I56aa4245be5d1f465b50842b1e92b9b53eff0303
Signed-off-by: Saad Karim <skarim@us.ibm.com>
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: I1e9baf4fa8fc3f0e08ebf6530317ccb97cab4653
Signed-off-by: Saad Karim <skarim@us.ibm.com>
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Ifd6385ba6ecfc47d326f3e4550cbb069874523c6
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Break more function out of support and add explicit unit tests.

Change-Id: I892b3d5f31da820b216a26bf9750394044ced72c
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Add explicit unit tests for TransactionContext

Change-Id: I28323e43483397eff45b5100989750a464744ec0
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

HandlerRegistry is used to track handlers based on the canonical name of
the chaincode. In addition to tracking handlers, it helps encapsulate
the launch and registration protocol.

Change-Id: I8013fca1dffa0d4a1cc28c6992fef5f51768a482
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Ic8023ec2f1661f67c8c34dd83ac12ba1e3b7b890
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Change-Id: Idbaf47a38825694c64b2d6cdbfa4358ac7acf9af
Signed-off-by: Saad Karim <skarim@us.ibm.com>
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>