OSAC-1568: Add e2e-test GitHub environment to osac-test-infra#107
Conversation
|
Warning Review limit reached
More reviews will be available in 50 minutes and 12 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository: osac-project/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (3)
WalkthroughAdds GitHub repository environment management to the ChangesGitHub Repository Environments Support
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@modules/common_repository/variables.tf`:
- Around line 134-148: Add two validation blocks to the environments variable
definition to catch issues at the module boundary. The first validation block
should ensure all environment names are non-empty strings by checking that no
element in the list has a blank name value. The second validation block should
ensure all environment names are unique by verifying that the count of distinct
names equals the total count of environments. Both validations should reference
the environments variable and provide clear error messages that explain why the
validation failed, since the for_each loop in main.tf at lines 106-108 uses
env.name as the key and will fail with duplicate-key or provider-time errors if
these constraints are violated.
🪄 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: Repository: osac-project/coderabbit/.coderabbit.yaml
Review profile: ASSERTIVE
Plan: Enterprise
Run ID: f5ee98eb-3bac-443f-b707-5b4653d68df3
📒 Files selected for processing (3)
modules/common_repository/main.tfmodules/common_repository/variables.tfrepositories.tf
3c3a968 to
062b52e
Compare
Add environment support to the common_repository module and create an e2e-test environment on osac-test-infra. This environment will be used by e2e workflows to authenticate to Vault via GitHub OIDC and retrieve test secrets.
062b52e to
9009fa6
Compare
Summary
environmentsvariable to thecommon_repositorymodulee2e-testenvironment onosac-test-infraWhy
E2e tests need secrets (cluster credentials, API tokens) from our local Vault instance on the CI runner. GitHub environments let workflows request OIDC tokens with an
environmentclaim, so Vault can restrict secret access to only workflows running ine2e-test— rather than allowing any workflow in the org.Other repos (fulfillment-service, osac-operator, etc.) will be onboarded in a follow-up PR once the full flow is validated on osac-test-infra.
Test plan
tofu planshows only the newgithub_repository_environmentresource for osac-test-infraSummary by CodeRabbit