Add --no-color option to disable color output

[caesarshift]

Description

Add --no-color option to disable color output

Related Issue

Fixes #890

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[netlify]

✅ Deploy Preview for zarf-docs canceled.

Name	Link
🔨 Latest commit	6c3a5ed
🔍 Latest deploy log	https://app.netlify.com/sites/zarf-docs/deploys/64d4f743c131c7000805b756

[caesarshift]

I created this as a draft MR in order to get feed back on this note

[YrrepNoj]

Replying to this comment @caesarshift left on the issue: #890 (comment)

The colored log message that says where we're loading the config file from is happening in the initViper(...) function.

That initViper(...) is called by the init function for root.go. Since it's called by an init function, we can not rely on any configuration to be set yet.

If we want to make it so the log message for which config file is being used follows the same configuration as the rest of the logs, we could just move this line to after we have called cliSetup(...)

[caesarshift]

Replying to this comment @caesarshift left on the issue: #890 (comment)

The colored log message that says where we're loading the config file from is happening in the initViper(...) function.

That initViper(...) is called by the init function for root.go. Since it's called by an init function, we can not rely on any configuration to be set yet.

If we want to make it so the log message for which config file is being used follows the same configuration as the rest of the logs, we could just move this line to after we have called cliSetup(...)

Based on your comment, I've added a follow-on commit that moves the print statements into the cli setup (moving it into the function preserves the order of the output to precede the current log level output)

[caesarshift]

FYSA, due to a merge conflict in src/config/config.go, I also rebased the branch.

[Racer159]

lgtm

[cmwylie19]

lgtm

[Racer159]

lgtm

[cmwylie19]

lgtm

[cmwylie19]

lgtm