hyperledger

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

• Blocked by #2378

As mentioned in [this comment] we temporary allow users to send extra bytes, but we print warning message. This was done to help SDK-developers.

After everything is stabilized we have to remove this and return an error every time something with extra bytes was sent

The tails file location after publishing a credential definition is not considering the white spaces in revocation tags, which leads to fail in uploading tails file but publishes the credential definition on the ledger