OLS-3327 - Bedrock tests#2980
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Warning Review limit reached
Next review available in: 48 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughAdds new Bedrock provider OLSConfig test fixtures for Anthropic, DeepSeek, and DeepSeek tool-calling scenarios. Introduces Bedrock IAM credential secret handling in the e2e installer module with a dedicated helper function. Wires new Bedrock test suites into both cluster e2e periodic and standard test scripts. ChangesBedrock e2e test support
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Script as e2e cluster script
participant Installer as ols_installer.py
participant Env as CI/Vault/Prow env vars
participant Cluster as OpenShift cluster
Script->>Installer: create_secrets(provider_name, creds)
Installer->>Installer: check provider_name starts with "bedrock"
Installer->>Installer: ensure_bedrock_iam_secret(creds)
Installer->>Env: read IAM or STS role env keys
alt required env vars missing
Installer-->>Script: skip, log message
else env vars present
Installer->>Cluster: oc create secret generic llmcreds
Cluster-->>Installer: secret created (or ignored if existing)
end
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@tests/e2e/utils/ols_installer.py`:
- Around line 288-291: The Bedrock credential selection in the helper that maps
`creds` to env keys currently treats every non-`iam_role` value as IAM, which
can hide bad discriminator values and break `create_secrets()` recovery. Update
the branching in the Bedrock env-key helper to accept only the supported
credential modes (`iam` and `iam_role`) and raise a clear failure for anything
else, so typos in `PROVIDER_KEY_PATH` do not silently choose the wrong key set.
In `@tests/scripts/test-e2e-cluster-periodics.sh`:
- Around line 75-76: The Bedrock tool-calling run is placed too early in the
periodic suite order, which can leave the tool-calling CR shape active for later
suites. Move the bedrock_deepseek_tool_calling run into the existing
tool_calling section in test-e2e-cluster-periodics.sh, alongside the other
tool-calling suites, so rhoai_vllm, rhelai_vllm, and certificates still run
after the non-tool-calling setup. Use the run_suite calls for
bedrock_deepseek_tool_calling and the surrounding tool_calling section as the
unique markers when relocating it.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: d69150a1-6347-4793-b261-2298cffdd1f4
📒 Files selected for processing (6)
tests/config/operator_install/olsconfig.crd.bedrock_anthropic.yamltests/config/operator_install/olsconfig.crd.bedrock_deepseek.yamltests/config/operator_install/olsconfig.crd.bedrock_deepseek_tool_calling.yamltests/e2e/utils/ols_installer.pytests/scripts/test-e2e-cluster-periodics.shtests/scripts/test-e2e-cluster.sh
0fe24bf to
75f3e95
Compare
addressing comments addressing comments
75f3e95 to
13fdbd7
Compare
|
/retest |
|
@JoaoFula: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
Description
add bedrock test files and adaptations to existing scripts
Type of change
Related Tickets & Documents
Checklist before requesting a review
Testing
Summary by CodeRabbit