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:
        

When a constant used by fabric-sdk-node is defined as an environment variable of OS and the value is boolean or number, it will not be parsed properly and will be treated as string value, and the constant will not be reflected.
For example, constant "DISCOVERY_AS_LOCALHOST = false" is defined, "false" is treated as string not boolean, so the behavior is the same as when "DISCOVERY_AS_LOCALHOST =

An unhandled custom rejection returns 500 ISE.
https://docs.rs/warp/latest/warp/reject/fn.custom.html
So every torii::Error case should be converted into explicit response in iroha_core::torii::routing::handle_rejection.
Remark that torii::Error has already impl Reply

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