devin-ai-integration[bot] 9c7ac0a6ea fix(helm): give the collector sidecar the pod PgBouncer env when database.connectionPool is enabled (#40660) ... The componentized chart rendered litellm.connectionPoolEnv into the gateway container only, so with database.connectionPool.enabled and gateway.collector.enabled the collector's Prisma client opened its own pool straight to Postgres instead of going through the pod-local PgBouncer. Render the same include in the collector container, drop the gateway.extraEnv workaround from the collector test, and add enabled/disabled regression assertions for the collector in both helm charts and the terraform aws and gcp modules, which already pass the pool env to their collector containers. The module READMEs note the IAM token-auth exception, where the collector keeps a direct connection by design. Co-authored-by: yassin <yassin@berri.ai> Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>		2026-09-11 02:07:04 +00:00
..
litellm	fix(helm): give the collector sidecar the pod PgBouncer env when database.connectionPool is enabled (#40660)	2026-09-11 02:07:04 +00:00
litellm-helm	fix(helm): give the collector sidecar the pod PgBouncer env when database.connectionPool is enabled (#40660)	2026-09-11 02:07:04 +00:00