fix(roxctl): default image flavor to opensource - #22754
Conversation
Signed-off-by: wangyusheng1985 <wangyusheng1985@users.noreply.github.com>
|
Hi @wangyusheng1985. Thanks for your PR. I'm waiting for a stackrox member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. 📝 SummarySummary by CodeRabbit
Walkthroughroxctl now uses the open-source image flavor by default. The previous non-release build override was removed. A test verifies the flag default and bound variable. ChangesImage flavor default
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to roxctl now consistently defaults omitted image settings to the open-source image flavor, with test coverage confirming the displayed and applied default. No current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
Description
Change roxctl's default
--image-defaultsvalue toopensourcefor both release and development builds. This avoids selecting build-dependent RHACS or development image repositories when the flag is omitted.User-facing documentation
Testing and quality
Automated testing
How I validated my change
AddImageDefaults.gofmtand the completeroxctl/common/flagspackage test suite.Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
The regression test verifies both the flag's displayed default and the destination value are
opensource; the package test suite provides additional coverage for the affected flags package.Validation observed for this change:
go test ./roxctl/common/flags -run TestAddImageDefaultsUsesOpenSourceByDefault -count=1gofmt -w roxctl/common/flags/imageFlavor.go roxctl/common/flags/imageFlavor_test.go && go test ./roxctl/common/flags -count=1Fixes #3029