At the moment, our chaincode pipeline (GO) does not have any support for vendoring packages. Given this limitation, our team has had [several times] to manually update the logic in the deploy script to vendor in dependencies. As you can imagine, this is tedious… and to avoid having to do this over and over again, let’s add this logic to this repo. To give you a concrete example, to leverage the CID library in a chaincode, you have to vendor it in… without the code in this PR, you’d have to manually write custom logic to vendor in this library.
BTW, this code has been successfully tested.
Note: As a future improvement to the code in this PR, we should also tackle getting libraries that are not in the Fabric binaries (this is still to be done, but first, wanted to tackle vendoring those libraries that are already in the Fabric binaries).
@jt-nti Can you review this PR?
At the moment, our chaincode pipeline (GO) does not have any support for vendoring packages. Given this limitation, our team has had [several times] to manually update the logic in the deploy script to vendor in dependencies. As you can imagine, this is tedious… and to avoid having to do this over and over again, let’s add this logic to this repo. To give you a concrete example, to leverage the CID library in a chaincode, you have to vendor it in… without the code in this PR, you’d have to manually write custom logic to vendor in this library.
BTW, this code has been successfully tested.
Note: As a future improvement to the code in this PR, we should also tackle getting libraries that are not in the Fabric binaries (this is still to be done, but first, wanted to tackle vendoring those libraries that are already in the Fabric binaries).
@jorgedr94 FYI