Skip to content

Fix: project config takes priority over env vars#10

Merged
desplega-bot merged 1 commit intomainfrom
fix-config-precedence
Feb 21, 2026
Merged

Fix: project config takes priority over env vars#10
desplega-bot merged 1 commit intomainfrom
fix-config-precedence

Conversation

@desplega-bot
Copy link
Contributor

Summary

  • Fixes config precedence so .qa-use-tests.json (project config) takes priority over environment variables (QA_USE_API_KEY, QA_USE_API_URL, QA_USE_DEFAULT_APP_CONFIG_ID)
  • Env vars now serve as fallbacks — only used when the config file doesn't set the value
  • Fixes the issue where global env vars (e.g. set by agent-swarm containers) silently override per-project configs

Test plan

  • Build passes (bun run build)
  • Lint passes (bun run check)
  • Existing tests pass (3 pre-existing E2E failures, same as main branch)
  • Manual: set QA_USE_API_KEY env var + .qa-use-tests.json with different api_key — config file value should win
  • Manual: remove api_key from .qa-use-tests.json — env var should be used as fallback

🤖 Generated with Claude Code

Previously, env vars (QA_USE_API_KEY, QA_USE_API_URL,
QA_USE_DEFAULT_APP_CONFIG_ID) always overrode values from the
project-level .qa-use-tests.json config file. This caused issues
when per-project configs were set up but a global env var (e.g.
from agent-swarm container) would silently override them.

Now the precedence is: project config > env vars > defaults.
Env vars only apply when the config file doesn't set the value.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
qa-use-mcp Ready Ready Preview, Comment Feb 21, 2026 1:14am

Request Review

@desplega-bot desplega-bot merged commit 4b6b236 into main Feb 21, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant