Trace is not outputted when --output=table

[tonglil]

As of v0.55.0, the CONFTEST_TRACE env var does not seem to set the conftest test --trace flag.

I expected the trace to still be displayed even if the output is set to something else.

[thevilledev]

Could not reproduce this on v0.55.0 or v0.56.0 (latest) on macOS 15.2. These commands produce identical output, sometimes in different order:

$ CONFTEST_TRACE=true conftest test examples/kubernetes/service.yaml -p examples/kubernetes/policy

$ conftest test --trace examples/kubernetes/service.yaml -p examples/kubernetes/policy

Looking at the code:

• internal/commands/default.go sets the env var prefix correctly
• internal/commands/test.go binds flagname trace correctly
• TestRunner struct in runner/test.go has a Trace field, and Viper binds struct fields to variables case-insensitively. Even though the struct tag mapstructure:"trace" is missing I think this should work.

Which environment was this failing on?

[tonglil]

Thanks for diving into this @thevilledev.

Upon closer inspection, I was setting the output flag to table, which seems to override trace, which I did not expect and falsely attributed to the flag not working.

[jalseth]

I agree this is not intuitive (or documented) behavior. I haven't had time to dig into why it is this way, so there may be a reason. PRs are welcome.

[thevilledev]

I noticed the tracing flag is only available for standard output. It's not passed to other output formats even if defined, on the other hand why would it be. I have a proposal to fix this in #1060 so that if the flag is defined, output format always defaults to standard.