docs(e2e): drop govcloud keys from the contributing starter env

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
This commit is contained in:
kerry 2026-09-17 21:47:21 +00:00
parent 5aec6d7bb6
commit 4b45fd5f44

View file

@ -23,10 +23,6 @@ The suites run against a live proxy, so bring one up first by running the litell
OPENAI_API_KEY="sk-..."
ANTHROPIC_API_KEY="sk-..."
GEMINI_API_KEY="..."
AWS_GOVCLOUD_ACCESS_KEY_ID="..."
AWS_GOVCLOUD_SECRET_ACCESS_KEY="..."
AWS_GOVCLOUD_BATCH_S3_BUCKET="..."
AWS_GOVCLOUD_BATCH_ROLE_ARN="..."
```
2. Bring up a Postgres and a Redis for the proxy to use. The repo-root `docker-compose.yml` already defines a Postgres on `5432`; a `docker run -p 6379:6379 redis:7` covers Redis. Point `DATABASE_URL` / `REDIS_HOST` / `REDIS_PORT` at whatever you run. Tests that read Redis directly default to the deployed shape (TLS + cluster mode) whenever `REDIS_HOST` is set, so for a local standalone Redis also set `REDIS_CLUSTER=false` and `REDIS_SSL=false` (plus `REDIS_PASSWORD` when your Redis requires auth)