Allowing hooks for the network's `prepare` phase

[lumtis]

ignite network chain prepare [launch-id]

is used when the chain launch is triggered and the validator must prepare their node for the chain launch. This command automatically setup the validator node in the idea of having a simple workflow for using Ignite chain. This command does:

• Generate the final genesis for the chain from the information on Ignite
• Set the persistent peers in the config.toml from the information on Ignite

Currently, if the validator has a more advanced setup and can't use this command, they should simply fetch the final genesis with ignite n chain show genesis [launch-id] and use it in their setup.

To make prepare command usable in an advanced setup, the command could accept hooks in order to perform side effects aside from generating the genesis.

The genesis generation algorithm should be deterministic, similar for all validators, and should not be customizable, but the setup and configuration of the validator node should be customizable.

[ntindle]

Hey! Thanks for making the issue.

One of the things that will be required of our deployments is setting up an IPFS node, and deploying another piece of software. We’d like to use ignite’s prepare to generate the configurations for those as well.

[ntindle]

Additional hooks on the validator side for join to install these softwares would also be amazing. Or even just telling them that it is required.

[lumtis]

Output from Ignite weekly call:

• Having the ability to have hooks for the initi and prepare processes (join only communicates with the Ignite Chain)
• FIrst explore for a universal solution for hooks
• Integrate hooks with Plugin functionality

Call to action

• [x] Create a new issue for the universal hook solution

[ntindle]

Issue created: https://github.com/ignite/cli/issues/2913

[lumtis]

Let's close this one for now, reopen it if a custom solution must be designed for prepare and init needs