9 views
-/https://github.com/berriai/litellm/issues/27287
GitHub · issue

#27287 [Feature]: allow toolset configuration via config

  • State: open
  • Author: @8de2fdb0
  • Labels: enhancement, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### The Feature

Would be grate to allow toolset configuration via config for deployments, api and database is a bit manual, config would be the easiest way to allow for clean deployments that can change stuff without breaking state.

### Motivation, pitch

Mostly relevant for deployment via terraform or similar infrastructure as code environments.

### What part of LiteLLM is this about?

Proxy

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

@asocial

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (3 events)
#0 of 0 · 31d18h24m18s ago — entered · #import:https:::github.com:berriai:litellm post #2543
-/https://github.com/berriai/litellm/issues/27287⭐5:1-/https://github.com/berriai/litellm/issues/32223
The left requires new proxy configuration plumbing, validation, lifecycle handling, and deployment-compatible integration, while the right is primarily behavioral clarification and documentation with little or no code change.
#0 of 0 · 31d18h20m17s ago · #import:https:::github.com:berriai:litellm post #2612
-/https://github.com/berriai/litellm/issues/27287⭐3:1-/https://github.com/berriai/litellm/issues/23976
The right issue is harder because it requires designing and integrating a new configuration surface across proxy parsing, validation, runtime behavior, persistence or deployment workflows, backward compatibility, and comprehensive testing. The left issue is comparatively scoped to diagnosing and fixing a startup migration-timeout regression, though environment-specific database behavior adds some uncertainty.
#0 of 0 · 31d17h47m39s ago — current · #import:https:::github.com:berriai:litellm post #3182
-/https://github.com/berriai/litellm/issues/27287⭐3:1-/https://github.com/berriai/litellm/issues/35578
The right-hand feature has broader architectural scope across configuration schema, proxy integration, persistence, validation, and backward compatibility, while the left-hand bug appears localized to fallback resolution and regression coverage.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search