test(google): boot the unified Google proxy fixture with a real master key

#42019 made the proxy refuse to start on a publicly known master key, and the
session fixture in tests/unified_google_tests started its in-process proxy with
sk-1234, so six tests errored in setup before reaching a provider

Give the fixture, the config it loads, and the SDK client the same non-default
key instead of the override the other harnesses took, so the boot check stays
live in this suite
This commit is contained in:
Claude 2026-09-20 08:48:39 +00:00
parent 6ef7b86748
commit d43fa7425b
No known key found for this signature in database
3 changed files with 3 additions and 3 deletions

View file

@ -14,7 +14,7 @@ try:
except ImportError:
GOOGLE_GENAI_SDK_AVAILABLE = False
MASTER_KEY = "sk-1234"
MASTER_KEY = "sk-unified-google-tests-4f9b2c7d8e1a"
PROMPT = "Reply with only the single word: pong"

View file

@ -34,7 +34,7 @@ from tests._vcr_conftest_common import ( # noqa: E402,F401
_verbose_state = VerboseReporterState()
PROXY_CONFIG_PATH = Path(__file__).parent / "google_genai_proxy_test_config.yaml"
PROXY_MASTER_KEY = "sk-1234"
PROXY_MASTER_KEY = "sk-unified-google-tests-4f9b2c7d8e1a"
PROXY_START_TIMEOUT_S = 30.0

View file

@ -14,7 +14,7 @@ router_settings:
RateLimitErrorRetries: 5
general_settings:
master_key: sk-1234
master_key: sk-unified-google-tests-4f9b2c7d8e1a
store_model_in_db: false
litellm_settings: