litellm/litellm-rust/crates/python-bridge
devin-ai-integration[bot] d6ffc554ec
feat(rust): align secret manager operation contexts (#42480)
* refactor(rust): simplify Python secret callbacks

* feat(rust): align secret manager operation contexts

* test(rust): port secret name validation cases

* fix(rust): restore secret manager CI checks

* fix(rust): validate Vault contexts and preserve rotation timeouts

---------

Co-authored-by: Yujong Lee <yujong@berri.ai>
2026-09-22 09:02:15 -07:00
..
benches refactor(rust): add types and core-utils crates, unify the provider error 2026-09-17 22:01:14 -07:00
src feat(rust): align secret manager operation contexts (#42480) 2026-09-22 09:02:15 -07:00
tests refactor(rust): add types and core-utils crates, unify the provider error 2026-09-17 22:01:14 -07:00
AGENTS.md refactor(rust): rename legacy callback adapter crate 2026-09-19 23:06:26 +00:00
build.rs feat: package Rust OCR bridge in LiteLLM wheel (#31267) 2026-06-25 12:32:55 -07:00
Cargo.toml feat(rust): align secret manager operation contexts (#42480) 2026-09-22 09:02:15 -07:00
README.md feat(rust-bridge): add cache and secret migration foundations (#42328) 2026-09-22 03:41:04 +00:00

Native OCR uses SecretSource with EnvironmentSecrets, preserving process-environment reads. Readable Python secret managers still make OCR decline to the existing Python implementation. ResolvedSecrets and the separate secret_manager_binding() snapshot are inactive foundations for a later rollout

Cache and secret-manager catalog entries remain Python-only, including when LITELLM_RUST=1. The new cache runtime is not connected to SDK or gateway caching

OCR provider requests use the shared litellm-http pool. AWS and Google secret-manager SDK clients keep their SDK transports, which do not yet inherit the pool's proxy, TLS, certificate, timeout, or observability configuration. Preserve those SDK transports and configure them equivalently instead of forcing them through reqwest