alexsong-oai 970111f6cb Allow configuring GCP project and location in provider settings (#56560) ...

## Why

Deriving a Vertex AI endpoint previously required environment variables. Allow the project and location to be specified directly in GCP provider configuration.

## What changed

- Add `model_providers.gcp.project_id` and `model_providers.gcp.location`, with each taking precedence over its corresponding environment variable. Keep `global` as the default location and preserve explicit `base_url` overrides.
- Validate configured endpoint fields and preserve them through thread configuration serialization.
- Apply built-in GCP defaults, including default command authentication, when checking managed provider requirements so unchanged requirements are accepted.

## Testing

Add coverage for endpoint precedence, invalid explicit configuration, provider construction, thread configuration round trips, and managed GCP requirement checks, including repeated model listing.

GitOrigin-RevId: c3704bcc0b7d4872374e2cae623fd24d75fb02b4

2026-10-23 18:50:54 +00:00

..

examples

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

scripts

Add remote thread config loader protos (#18892)

2026-04-23 10:06:05 -07:00

src

Allow configuring GCP project and location in provider settings (#56560)

2026-10-23 18:50:54 +00:00

BUILD.bazel

Embed defaults in the packaged config layer (#38179)

2026-08-12 12:15:47 +00:00

Cargo.toml

Require managed configuration from the configured server (#56055)

2026-10-22 02:15:00 +00:00

defaults.toml

Make environment context date and timezone configurable (#52164)

2026-10-08 16:27:10 +00:00