Keep step-runner operator logs out of docker job traces

Arran Walkerrequested to merge
ajwalker/steps-operator-logger into main

What does this MR do?

Keep step-runner operator logs out of docker job traces

Pass di.WithOperatorLogger(discard) when building the serve container so those logs are dropped. Job output (via the gRPC log stream) is unaffected.

Why was this MR needed?

The docker executor tees the 'steps serve' container's stderr into the job trace (executors/docker/steps.go). step-runner's operator logs (e.g. a job failure) default to that stderr, surfacing in traces as noise that's already reported via the job status.

What are the relevant issue numbers?

Closes #39571 (closed)

Edited by Arran Walker

Merge request reports