Closed rtang03 closed 3 years ago
This is a more difficult task than imagined. That is not only impacting enrollAdmin. It affects everything in package/operator, because all admin task rely on this low-level api "fabric-client". Unsure if "fabric-client" can be totally removed.
I find that "fabric-network" v2.2.3 is in conflict with installed "fabric-client" v1.4.x And, therefore, I need to drop "fabric-client" entirely.
Unfortunately, there is negative impact, which getQueries
function in "packages/operator" will be dropped as well.
That is not an impact. By Hyperledger official direction, the SDK will no longer add / perform administrative function. The dropped administrative API, can be fulfilled by Hyperledger Explorer.
The administrative API inside "packages/operator" will thereafter focus on Fabric CA server admin functions.
During the version upgrade from fabric-network from v2.1.x to v2.2.3. There is an error below:
Currently, enrollAdmin is using fabric-client v1.4.x. By Fabric documentation below, it recommends a migration.
https://hyperledger.github.io/fabric-sdk-node/release-2.2/tutorial-migration.html
Sooner or later, the use fabric-client v1.4.x should be replaced. It mainly impacts the
enrollAdmin
under packages/operator.This is high priority item, it blocks, simply because the enrollAdmin cannot run properly when
fabric-network
's version is bumped.148
149
150