Description
When using native Terraform steps in Harness pipelines, Terraform's standard output (
stdout
) and standard error (
stderr
) are captured and displayed together in the execution log console.
Currently,
stdout
messages are published with the
INFO
log level, while
stderr
messages are published with the
ERROR
log level. Since both streams are processed as their output arrives, their messages can become interleaved.
This is particularly problematic when Terraform encounters validation or configuration errors. Multiline error messages can become fragmented across numerous lines of Terraform plan output, making them difficult to read and troubleshoot.
There is currently no built-in option in the pipeline execution console to filter these logs by severity or display the two streams separately.
Proposed Enhancement
Introduce
log-level filtering in the pipeline execution console
, allowing users to:
  • Filter execution logs by level, such as
    INFO
    and
    ERROR
    .
  • View only error messages without unrelated standard output appearing between them.
  • Switch between filtered and unfiltered views without downloading the logs.
  • Preserve the existing combined log view as the default behavior.
Ideally, the filtering capability would be available directly in the execution log interface and could benefit other pipeline step types that publish different log levels.
Expected Benefits
  • Improved readability of Terraform validation and execution errors.
  • Faster identification and troubleshooting of failures.
  • Reduced need to download logs and manually filter them.
  • A more efficient debugging experience for users working with verbose pipeline steps.
Current Workaround
Users must download the execution logs and manually filter them by
ERROR
or
INFO
to isolate the relevant output.
Providing this functionality directly in the UI would significantly improve the troubleshooting experience.
Created by Pedro Mastelaro
·