Verbose flags for for network or scaffold sub-commands

[amitkarpe]

Is your feature request related to a problem or issue you encountered? Please describe.
Can we have Verbose flags for for network or scaffold sub-commands?

Describe the solution you'd like
How to enable verbose logging (on shell) for network or scaffold sub-commands?

As of now we have verbose option for all sub-commands of ignite chain
Like ignite chain serve -v or ignite chain simulate -h or ignite chain build -h

It will be great if have similar options for other sub-commands like ignite network or ignite scaffold.

Describe alternatives you've considered
Also can we have environment variables which will be detected by ignite command to set verbosity of log messages.
e.g.
IG_VERBOSE=WARN
We may use similar structure from app cli --log_level from Global Flags.
--log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")

[aljo242]

We are working on adding more verbosity to serve with a debugging feature and more !

[amitkarpe]

A debugging feature is more from Developer point view. It will be helpful to have more verbose logs to troubleshoot or understand overall working of the blockchain.

example: ignite chain serve -v gives more logs which helps to understand steps executed/involved while starting blockchain.

[IOCHAINCD] 7:36AM INF starting node with ABCI Tendermint in-process
[IOCHAINCD] 7:36AM INF service start impl=multiAppConn module=proxy msg={}
[IOCHAINCD] 7:36AM INF service start connection=query impl=localClient module=abci-client msg={}
[IOCHAINCD] 7:36AM INF service start connection=snapshot impl=localClient module=abci-client msg={}
[IOCHAINCD] 7:36AM INF service start connection=mempool impl=localClient module=abci-client msg={}
[IOCHAINCD] 7:36AM INF service start connection=consensus impl=localClient module=abci-client msg={}
[IOCHAINCD] 7:36AM INF service start impl=EventBus module=events msg={}
[IOCHAINCD] 7:36AM INF service start impl=PubSub module=pubsub msg={}
[IOCHAINCD] 7:36AM INF service start impl=IndexerService module=txindex msg={}
[IOCHAINCD] 7:36AM INF ABCI Handshake App Info hash= height=0 module=consensus protocol-version=0 software-version=latest-9be3c559
[IOCHAINCD] 7:36AM INF ABCI Replay Blocks appHeight=0 module=consensus stateHeight=0 storeHeight=0
[IOCHAINCD] 7:36AM INF initializing blockchain state from genesis.json
[IOCHAINCD] 7:36AM INF asserting crisis invariants inv=1/12 module=x/crisis name=distribution/nonnegative-outstanding
[IOCHAINCD] 7:36AM INF asserting crisis invariants inv=2/12 module=x/crisis name=distribution/can-withdraw
[IOCHAINCD] 7:36AM INF asserting crisis invariants inv=3/12 module=x/crisis name=distribution/reference-count
[IOCHAINCD] 7:36AM INF asserting crisis invariants inv=4/12 module=x/crisis name=distribution/module-account
...
...
...
[IOCHAINCD] 7:36AM INF asserted all invariants duration=1.912805 height=0 module=x/crisis
[IOCHAINCD] 7:36AM INF created new capability module=ibc name=ports/transfer

So similar information needed for also every command/sub-command based operations. May be not subcommands but selected sub-commands, will help a lot for troubleshooting 🙏🏽
This will lower the load on developer and most of the errors/technical issues will be report with more details. Also community able to understand and build knowledge based to address those issues.

Just like any other binary/project (e.g. kubernetes ☸) ignite can verbose flags to output more text/logs on stdout.

[aljo242]

You can now run in debug with the IGNT_DEBUG=1 environment variable !