Reduce compile output noise from container image validation#31232
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
Reduce container image validation verbosity
Reduce compile output noise from container image validation
May 9, 2026
Copilot created this pull request from a session on behalf of
pelikhan
May 9, 2026 16:05
View session
Contributor
There was a problem hiding this comment.
Pull request overview
Reduces compile-time log noise by removing per-tool “container image validated” success messages while keeping container image validation logic and error reporting unchanged.
Changes:
- Removed verbose per-image success output from
validateContainerImages. - Kept the existing docker validation execution and error aggregation behavior intact.
Show a summary per file
| File | Description |
|---|---|
| pkg/workflow/runtime_validation.go | Removes verbose per-image success printing during container image validation to reduce compile output clutter. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
| @@ -214,8 +214,6 @@ func (c *Compiler) validateContainerImages(workflowData *WorkflowData) error { | |||
| // Validate the container image exists using docker | |||
| if err := validateDockerImage(containerImage, c.verbose, c.requireDocker); err != nil { | |||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✨ Enhancement
Repeated per-workflow container validation success lines were cluttering compile output and obscuring higher-signal messages (e.g., warnings). This update reduces that noise while preserving existing container image validation behavior.
What does this improve?
Compile output no longer emits
ℹ ✓ Container image validated: ...for each validated tool image, making workflow-level results and warnings easier to scan.Why is this valuable?
The previous output duplicated low-value success information across many workflows, increasing log volume without adding actionable signal.
Implementation approach:
Removed the verbose success print in
validateContainerImages(pkg/workflow/runtime_validation.go) while leaving validation execution, error collection, and warning/error paths unchanged.