The devcontainer CLI exposes --log-level info|debug|trace as a global flag, but nothing reads it today — every event from the engine renders at the same verbosity in cmd/devcontainer/events.go.
Two ways forward:
- Filter events in
printEvent based on level (e.g. BuildLogEvent / LifecycleOutputEvent only at debug+). Cheap, CLI-local, no library change.
- Wait until the library grows a verbosity knob on
EngineOptions and honor that instead.
Lowest-friction option is (1). Until either lands, the flag is misleading and should either be removed or documented as a no-op.
The
devcontainerCLI exposes--log-level info|debug|traceas a global flag, but nothing reads it today — every event from the engine renders at the same verbosity incmd/devcontainer/events.go.Two ways forward:
printEventbased on level (e.g.BuildLogEvent/LifecycleOutputEventonly atdebug+). Cheap, CLI-local, no library change.EngineOptionsand honor that instead.Lowest-friction option is (1). Until either lands, the flag is misleading and should either be removed or documented as a no-op.