1. 01 Dec, 2018 1 commit
  2. 17 Oct, 2018 1 commit
  3. 12 Sep, 2018 1 commit
  4. 05 Sep, 2018 1 commit
  5. 10 Jul, 2018 4 commits
    • Jason Yellick's avatar
      FAB-10979 PackageProvider provides code package · 954f350c
      Jason Yellick authored
      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: default avatarJason Yellick <jyellick@us.ibm.com>
    • Jason Yellick's avatar
      FAB-10978 Remove spec from container_runtime · e3d70517
      Jason Yellick authored
      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: default avatarJason Yellick <jyellick@us.ibm.com>
    • Jason Yellick's avatar
      FAB-10977 Extract lifecycle to interface · b1dd84b9
      Jason Yellick authored
      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: default avatarJason Yellick <jyellick@us.ibm.com>
    • Jason Yellick's avatar
      FAB-10976 Move lifecycle to its own package · 305c5ad9
      Jason Yellick authored
      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
      Change-Id: I8883b9fc39d7b23d42ba6df31389e5a9df248457
      Signed-off-by: default avatarJason Yellick <jyellick@us.ibm.com>
  6. 22 May, 2018 2 commits
  7. 14 May, 2018 1 commit
  8. 10 May, 2018 3 commits
  9. 02 May, 2018 2 commits
  10. 25 Apr, 2018 2 commits
  11. 23 Apr, 2018 2 commits