pass component prerelease image tag to E2E tests#86
Conversation
Replace the hardcoded charts_name (already defaulted in the receiver) with component_image_tags so system tests run against the actual pre-release image instead of the default release. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughModified Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Summary:
|
1 similar comment
|
Summary:
|
Summary
component_image_tagsin the E2E dispatch payload so system tests run against the actual built image instead of the default releasecharts_namefrom the dispatch (receiver already defaults it tokubescape-operator) to stay within GitHub's 10 top-level key limit onclient_payloadCOMPONENT_IMAGE_TAGSin receiver) and kubescape/node-agent (same change in its local workflow copy)How it works
The dispatch now includes
component_image_tags=<component>-tag=<prerelease-version>(e.g.,operator-tag=v0.2.42-prerelease). The receiver forwards it tob-run-system-tests-self-hosted.yamlwhich already supportsCOMPONENT_IMAGE_TAGSand appends it to--kwargsforsystest-cli.py.Test plan
component_image_tags🤖 Generated with Claude Code
Summary by CodeRabbit