would be great if you consider a better onboarding experience for new nodes that should join a existing network.
The problem here is (mainly when using docker, or other ways to automate nodes joining a network) that it is quite awkward at the moment to onboard a node.
When a node cannot join a network it just exits with a message.
To automate this I had to do a lot of scripting like:
- grep the account address (to hand it over to some node in the network for granting)
- start an additional rest service on the instance just to be able to query the account address from outside because the node immediately stops when not able (allowed) to connect
- hard to get the account address without again trying to connect and grep from the error message if you missed it
- do a bash for loop trying to connect every minute and see if permission were granted
I think dockerization of MultiChain and something like Multichain as a Service offerings need a better handling in this case.
Maybe the node can keep running and tries connect polling itself?
Maybe when it keeps running it has a minimal json rpc interface that allows to query:
- the generated MC account
- some information that are available event without connectivity to another network (e.g. which network it wants to join etc...)