inference-bot 7f04920327 broker: retire the old LiteLLM key before re-creating a same-name key ...

LiteLLM requires unique key aliases, so re-creating a key with an existing
(email, name) pair 400s ('alias already exists') — breaking key rotation
from the dashboard. The stored LiteLLM hash lets us retire the old key
first; the ON CONFLICT upsert then tracks the new key.

Surfaced by the LibreChat sandbox work: the portal chat-key rotation for
an SSO member failed with exactly this 400.

2026-10-17 18:00:49 -06:00

..

__init__.py

Scaffold member portal: OC webhook + Cloudron user mgmt + LiteLLM key injection

2026-09-04 17:06:27 -06:00

main.py

broker: retire the old LiteLLM key before re-creating a same-name key

2026-10-17 18:00:49 -06:00