Require auth managers to receive routing configuration (#34650)

## Why

Auth managers should use the application's resolved HTTP client factory instead
of silently falling back to the transport's default proxy behavior.

## What changed

- Make `AuthRouteConfig` required when constructing an `AuthManager` or
  `AuthConfig`.
- Pass each production caller's resolved routing configuration through without
  wrapping it in an optional value.
- Add a test helper that explicitly selects the transport-default proxy policy
  for callers that do not exercise custom routing.

GitOrigin-RevId: d89a3b1f8b5d4007650cdac0aae241c94d598580
This commit is contained in:
Michael Bolin authored and copyberry committed 2026-07-22 01:35:06 +00:00
1 parent f899a79c03
commit a26bc337cf
19 files changed
+75 -53

No files matched your search

+2 -2
View File
@@ -1250,8 +1250,8 @@ impl AuthManagerConfig for Config {
self.chatgpt_base_url.clone()
}
fn auth_route_config(&self) -> Option<AuthRouteConfig> {
Some(Config::auth_route_config(self))
fn auth_route_config(&self) -> AuthRouteConfig {
Config::auth_route_config(self)
}
}