Repository navigation
Build yq for Conforma CLI images, avoid needless kubectl cross-compiles - #3663
simonbaird wants to merge 2 commits into
Conversation
I was thinking I would need it for the "inject data source" script, but I realized I could get away with using jq. Despite that, we've have been talking about doing this for a number of other reasons recently, perhaps it's worth while either way. Ref: https://redhat.atlassian.net/browse/EC-2377 Assisted-by: gpt-6-sol
I don't think there was ever any good reason to do all that cross-compiling of kubectl. I think it was done that way since that's how the ec build was done. It seems like we don't copy the cross-compiled binaries over to the final image anyway which would have to mean they're 100% unused. https://redhat.atlassian.net/browse/EC-2365 Assisted-by: gpt-6-sol
PR Summary by QodoAdd yq to Conforma images and build kubectl only for the image platform
AI Description
Diagram
High-Level Assessment
Files changed (6)
|
Code Review by Qodo
View low (1)🟡 **Low** 1. Kubectl image builds can depend on cgo
|
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
<!-- fullsend:risk-assessment --> DetailsScore 3 (elevated) driven by three high-risk Tier 1 signals: protected Dockerfile paths, two new Go dependency files (go.mod/go.sum), and zero test coverage, offset by a known non-bot author, no security-sensitive changes, and very low git churn/regression history in Tier 2. |
|
Looks good to me Labels: PR modifies Dockerfiles, adds a new Go tool module (tools/yq/), and changes build infrastructure. <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> |
Summary
The yq packaging is useful independently of the planned runtime-data work; that work is not included in this PR.
Verification
bash -n build.shgit diff --check upstream/main...HEADCGO_ENABLED=0);yq --versionreports v4.53.3.Related: EC-2377, EC-2365.