7 views
-/https://github.com/berriai/litellm/issues/25947
GitHub · issue

#25947 [Bug]: Vector stores from config.yaml are not added

  • State: open
  • Author: @chim1aap
  • Labels: bug, proxy, llm translation

### Check for existing issues

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

### What happened?

When configuring vector stores through the config.yaml

### Steps to Reproduce

0. Docker compose file: ``` services: litellm: image: docker.litellm.ai/berriai/litellm:v1.83.3-stable volumes: - ./litellm-config.yaml:/app/config.yaml command: - "--config=/app/config.yaml" ports: - "4000:4000" environment: DATABASE_URL: "postgresql://llmproxy:dbpassword9090@db:5432/litellm" STORE_MODEL_IN_DB: "True" # allows adding models to proxy via UI PGVECTOR_DATABASE_URL: "postgresql://pgvector_user:pgvector_pass@pgvector:5432/pgvector_db" env_file: - .env-litellm depends_on: db: condition: service_healthy restart: unless-stopped

db: # Main PostgreSQL database used by LiteLLM for proxy state image: postgres:16 restart: always container_name: litellm_db environment: POSTGRES_DB: litellm POSTGRES_USER: llmproxy POSTGRES_PASSWORD: dbpassword9090 ports: - "5432:5432" #volumes: # - postgres_data:/var/lib/postgresq…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d17h42m47s ago — entered · #import:https:::github.com:berriai:litellm post #3148
The left issue is harder because it likely spans configuration parsing, startup initialization, database-backed state, and end-to-end proxy behavior, with broader regression-test coverage. The right issue appears comparatively localized to credential propagation and request-header construction.
The left task has substantially broader scope: it requires designing and maintaining a new external-provider integration across both library and proxy layers, including configuration, lifecycle behavior, compatibility, and comprehensive testing. The right task is a localized proxy configuration/loading defect with a narrower diagnostic and remediation path.
#0 of 0 · 31d17h18m27s ago — current · #import:https:::github.com:berriai:litellm post #3541
Issue 23841 spans multiple translation paths, content formats, provider routing modes, and integration regressions, creating broader implementation and testing risk. Issue 25947 appears more localized to proxy configuration loading and vector-store initialization.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search