ripe hornet
Is there a way to not print the stdout of a withExec call to the logs?
I have a rather long json object that is being returned and makes it much harder to see what is going on if it shows in the logs.
I also tried using the redirectStdout which directs the results to a file, but it still shows in the logs.
ripe hornet
I did find a work around that I posted on this issue as well, but it would be nice if redirectStdout prevented the stdout from showing in the logs
https://github.com/dagger/dagger/issues/8798
brazen ingot
I did find a work around that I posted on this issue as well, but it would be ni...
SGTM! This is a tricky one I think because the output that you see in the progress comes from the engine OTEL channel and not the executor itself, so I'm not sure how straightforward is to achieve this at the telemetry level per exec operation. @digital magnet might have a better idea 🙏
digital magnet
brazen ingot
should be easy to change: <https://github.com/dagger/dagger/blob/918cfde1e9a9d67...
that's for the executor metadata, correct? IIUC the OP needs disabling the output that gets sent via buildkit's OTEL which I'd think that's something internal?
i.e: they'd still need to get the stout/err via the Dagger method call but they'd like to remove it from the progrock span log output
In the executor link you've shared above are the procinfo.Stdour/err writers the ones that get ultimately get sent via OTEL?