From 4b45fd5f44a6a85b0475bf470a5abe14db3eb38a Mon Sep 17 00:00:00 2001 From: kerry Date: Thu, 17 Sep 2026 21:47:21 +0000 Subject: [PATCH] docs(e2e): drop govcloud keys from the contributing starter env Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- tests/e2e/CONTRIBUTING.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/tests/e2e/CONTRIBUTING.md b/tests/e2e/CONTRIBUTING.md index 75270250f30..20073e5d68f 100644 --- a/tests/e2e/CONTRIBUTING.md +++ b/tests/e2e/CONTRIBUTING.md @@ -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)