Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add options to auto-register channels on service startup #12

Open
ziegfried opened this issue Sep 3, 2019 · 0 comments
Open

Add options to auto-register channels on service startup #12

ziegfried opened this issue Sep 3, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@ziegfried
Copy link
Contributor

So I need to read the docs/code a bit more, but we could possibly add a pollPeerForJoinedChannels function here so that we don't need to explicitly wait for a GET request on the server. This could be a configuration flag that we set, like 'AUTO_REGISTER_CHANNELS` or something like that.

The peer channel list function does what we need:
https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/peerchannel.html

The code on the CLI side invokes the cscc chaincode on the peer node with the GetChannels argument:
https://github.com/hyperledger/fabric/blob/release-1.4/peer/channel/list.go#L53

You can see the cscc chaincode here:
https://github.com/hyperledger/fabric/blob/master/core/scc/cscc/configure.go#L211

Access to cscc requires that the Fabric Logger user have the correct ACL policy set.

The node SDK is really poorly documented but I think this is the right place to look for submitted transactions:
https://fabric-sdk-node.github.io/release-1.4/tutorial-handlers.html

Originally posted by @jeffywu in #10

@dexa187 dexa187 added the enhancement New feature or request label Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants