feat: file-based env vars for e2e tests#1
Conversation
Replace hardcoded AWS account IDs, subnet IDs, and other
environment-specific values with file.read("env/...") pattern.
CI writes env files from GitHub repo variables (${{ vars.* }}).
Workflow versions updated to v2.19.1 + feat/kcl-env-files.
Implements [[tasks/e2e-env-vars-via-files]]
Update e2e workflow ref from feat/kcl-env-files to v2.19.1.
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
Published Crossplane PackageThe following Crossplane package was published as part of this PR: Package: ghcr.io/hops-ops/aws-dns-stack:pr-1-6a159e82f711f382383a0a78c4bbbfa440d2843b |
Summary
file.read("env/...")pattern${{ vars.* }}) via shared e2e workflow v2.19.1tests/**/env/to.gitignoreWhy
KCL cannot read environment variables but can read files. This makes e2e tests fully portable — enterprise forks only need to set their own GitHub repo variables, no code changes needed.
Test plan
🤖 Generated with Claude Code