mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-16 23:41:43 +00:00
2849aee57d
* fix(health): probe test_connection with the credential the request names /health/test_connection matches the request's model string against the configured deployments and merges the match's litellm_params underneath the request. A request that named a stored credential but no key of its own still satisfied the "request sets no connection fields" test, so it inherited the matched deployment's api_key and api_base, and load_credentials_from_list then skipped the named credential because api_key was already set. A wildcard route covering the model is enough to match, so the Add Model page's Test Connect probed with an unrelated deployment's key while echoing back the credential that was selected. Naming a credential the configuration does not name now withholds the configuration's credential fields, the same set already withheld from a request that supplies its own endpoint. Naming no credential still inherits them, as documented. * test(health): drop test docstrings that restate their own names * test(health): assert the credential probe on the wire, not on the call args The connection-test regressions patched litellm.ahealth_check and read the params handed to it. Driving the endpoint through the app with respx faking the upstream instead lets the real credential resolution run, so the tests assert the key and host that actually go out, which is what the bug was about. It also drops three of the five patched proxy internals; the two that are left are proxy-global wiring with no injection seam, the same ones the image_edit connection test already has to reach for. * chore(ui): regenerate schema.d.ts for the test_connection docs change |
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||