Add -no-color option

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave “+1” or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Please add the option -no-color to cdk.

A lot of users run cdk in a context where the output is not rendered by the system, but instead used for further computation or redirected to other sinks, that cannot interpret terminal formatting. The additional formatting strings makes log reading very difficult. Thank you very much for your work and for your attention. 👍

References

https://www.terraform.io/cli/commands/apply#no-color

[ansgarm]

Ah, thank you for explaining! Yeah, I’d be cautious about doing a string search for Error: as well. Unfortunately there is no better solution at the moment while still using the CDKTF CLI. That said, you could certainly invoke the Terraform CLI directly in the cdktf.out/stacks/<your-stack> directory and pass the -json option to terraform apply. Depending on the system you are trying to build, this might be worth the effort.

Regarding the color: While FORCE_COLOR disables all the color the CDKTF CLI uses, it still invokes the Terraform CLI under the hood (and redirects its output). Until we support a proper -no-color option you should be able to disable the colored output for the Terraform CLI by additionally setting TF_CLI_ARGS="-no-color".

[nekhebit]

The output given by cdk is really verbose. It is good for a human to go through it and understand what is going on. It is not so good if you want to output it to a existing logging structure. I would like to either receive a confirmation of success or the error that was generated, without the terraform formatted string/redundant information.

A quick and dirty solution would be to parse the output and search for the Error: string and get the content until the next new line, but everything in me is screaming against it. Maybe there is already an option to get this information without having to resort to this terrible solution. 😁

About the FORCE_COLOR=0: Im still getting color. 😭 Less than before, but still some color:

From pod’s log:

From console with FORCE_COLOR=0

From console with FORCE_COLOR=1