Repository navigation
fix(ci): use k8s pod env vars for API keys instead of GitHub secrets - #782
Conversation
API keys (HF_TOKEN, OPENAI_API_KEY, ANTHROPIC_API_KEY, XAI_API_KEY) are now injected as env vars directly on k8s runner pods via secretKeyRef. The workflow env: blocks were overriding pod env vars with empty strings because the GitHub secrets were removed, causing all external API tests to fail with "ANTHROPIC_API_KEY not set". What changed: - .github/workflows/e2e-gpu-job.yml: remove HF_TOKEN, OPENAI_API_KEY, XAI_API_KEY, ANTHROPIC_API_KEY from env block - .github/workflows/pr-test-rust.yml: remove HF_TOKEN, OPENAI_API_KEY, XAI_API_KEY, ANTHROPIC_API_KEY from 3 env blocks - .github/workflows/nightly-benchmark.yml: remove HF_TOKEN from 3 env blocks Signed-off-by: Simo Lin <linsimo.mark@gmail.com>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (3)
📝 WalkthroughWalkthroughEnvironment variables containing API keys and tokens (HF_TOKEN, OPENAI_API_KEY, XAI_API_KEY, ANTHROPIC_API_KEY) are removed from multiple GitHub Actions workflow files across E2E test and benchmark job steps. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
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)
📝 Coding Plan
Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2b91a48dc9
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| - name: Run E2E tests | ||
| env: | ||
| OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} | ||
| XAI_API_KEY: ${{ secrets.XAI_API_KEY }} | ||
| ANTHROPIC_API_KEY: ${{ secrets.CLAUDE_API_KEY }} | ||
| BRAVE_MCP_HOST: ${{ matrix.setup_agentic_deps && 'brave-search-mcp' || '' }} |
There was a problem hiding this comment.
Keep vendor API keys wired for e2e-vendor jobs
This step now relies entirely on runner-level API key environment variables, but in the checked-in ARC runner configs (scripts/k8s-runner-resources/runner-values-*.yaml) the runner container env only defines Docker-related vars and does not inject OPENAI_API_KEY, XAI_API_KEY, or ANTHROPIC_API_KEY. The vendor test fixture fails hard when those vars are absent (e2e_test/fixtures/setup_backend.py checks api_key_env and calls pytest.fail), so deployments that follow the repo’s runner manifests will fail these jobs after this change unless a fallback (for example GitHub secrets) is kept or the runner env injection is added in-repo.
Useful? React with 👍 / 👎.
…mg-project#782) Signed-off-by: Simo Lin <linsimo.mark@gmail.com>
…mg-project#782) Signed-off-by: Simo Lin <linsimo.mark@gmail.com>
Summary
secretKeyRefProblem
GitHub secrets (
HF_TOKEN,OPENAI_API_KEY,CLAUDE_API_KEY,XAI_API_KEY) were removed from the repo. The workflow env blocksANTHROPIC_API_KEY: ${{ secrets.CLAUDE_API_KEY }}resolved to empty strings, overriding the pod-level env vars and causing all external API tests to fail.What changed
HF_TOKEN,OPENAI_API_KEY,XAI_API_KEY,ANTHROPIC_API_KEYHF_TOKEN,OPENAI_API_KEY,XAI_API_KEY,ANTHROPIC_API_KEYfrom 3 env blocksHF_TOKENfrom 3 env blocksTest plan
anthropic-messagesjob no longer fails with "ANTHROPIC_API_KEY not set"Summary by CodeRabbit