Is your feature request related to a problem? Please describe.
When executing zarf package deploy from a command line, the erroring reporting seems inconsistent.
Example 1:
A deployment.yaml is missing spec.selector.
zarf output:
Example 2:
A deployment.yaml is missing spec.template.metadata
zarf output:
In both scenarios, when trying to review/troubleshoot using the associated log file with linux tools like vi, nano or simply cat the log file piped to less (cat /var/folders/bh/l8qqtz8x57j5vjd8sd33sxt40000gn/T/zarf-2022-10-12-08-46-18-3119412142.log | less) the log file is difficult to read due to the color flags.
Describe the solution you'd like
For example 1, similar logging output to example 2.
The ability to use basic linux tools to easily review and examine the log file for troubleshooting.
Describe alternatives you've considered
Manually testing yaml files before building a zarf package (i.e. kubectl apply -f deployment.yaml) to avoid the "WARNING Unable to complete helm chart install/update" messages and application deployment failure.
Don't currently have a good alternative to viewing the logs. I can investigate other editing tools.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
When executing zarf package deploy from a command line, the erroring reporting seems inconsistent.
Example 1:
A deployment.yaml is missing spec.selector.
zarf output:
Example 2:
A deployment.yaml is missing spec.template.metadata
zarf output:
In both scenarios, when trying to review/troubleshoot using the associated log file with linux tools like vi, nano or simply cat the log file piped to less (cat /var/folders/bh/l8qqtz8x57j5vjd8sd33sxt40000gn/T/zarf-2022-10-12-08-46-18-3119412142.log | less) the log file is difficult to read due to the color flags.
Describe the solution you'd like
For example 1, similar logging output to example 2.
The ability to use basic linux tools to easily review and examine the log file for troubleshooting.
Describe alternatives you've considered
Manually testing yaml files before building a zarf package (i.e. kubectl apply -f deployment.yaml) to avoid the "WARNING Unable to complete helm chart install/update" messages and application deployment failure.
Don't currently have a good alternative to viewing the logs. I can investigate other editing tools.
Additional context
Add any other context or screenshots about the feature request here.