refactor: drop the litellm-pgvector vector store #19

Merged
marti merged 2 commits from feature/remove-litellm-pgvector into main 2026-10-02 19:50:14 +02:00
Owner

Summary

  • Remove the litellm-pgvector connector module and its podman container from cum-tools.
  • Stop provisioning the litellm_vectors database, the pgvector extension, and the one-shot install unit in cum-services.
  • Remove the vector store registry entry from LiteLLM and the Open-WebUI external knowledge source.
  • Drop the litellm_vector_store_id var and the litellm-pgvector port wiring.

Testing

  • Not run
## Summary - Remove the `litellm-pgvector` connector module and its podman container from cum-tools. - Stop provisioning the `litellm_vectors` database, the `pgvector` extension, and the one-shot install unit in cum-services. - Remove the vector store registry entry from LiteLLM and the Open-WebUI external knowledge source. - Drop the `litellm_vector_store_id` var and the `litellm-pgvector` port wiring. ## Testing - Not run
Nothing used the LiteLLM vector store, so the connector container, its
registry entry in LiteLLM and Open WebUI's external knowledge source
pointing at the same tables all go. The config.py patch and the pgvector
python dep only existed to feed that source, so they go with it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The only consumer was the litellm-pgvector connector on cum-tools. This
also takes away the one new database that made postgresql-setup run
CREATE DATABASE against template1 after the glibc 2.42 bump.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
marti merged commit 54429fddce into main 2026-10-02 19:50:14 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cumsek/nix!19
No description provided.