litellm - 💡(How to fix) Fix [Bug]: Helm chart migrations-job.yaml doesn't URL-encode PostgreSQL password [1 participants]

Check for existing issues

• I checked existing issues and this bug has not been reported yet.

What happened?

The migrations-job.yaml template constructs DATABASE_URL by directly interpolating postgresql.auth.password into the URL without URL-encoding. Passwords containing URL-special characters (/, +, =) cause the migration job to fail with Prisma error P1013:

Error: P1013: The provided database string is invalid. invalid port number in database URL.

Expected behavior: The migration job should handle passwords with special characters the same way the main deployment does.

Steps to Reproduce

1. Set a base64-encoded password in postgresql.auth.password (e.g. IdS4Ahqw4rpvBgP8q/BK/A==) — base64 commonly contains /, +, and =
2. Deploy with migrationJob.enabled: true (default)
3. The migration job gets DATABASE_URL=postgresql://litellm:IdS4Ahqw4rpvBgP8q/BK/A==@release-postgresql/litellm
4. Prisma fails to parse the URL because / is interpreted as a path separator

The main deployment is unaffected because it passes individual env vars (DATABASE_HOST, DATABASE_PASSWORD) and LiteLLM's Python code URL-encodes the password via urllib.parse.quote_plus() in construct_database_url_from_env_vars(). The migration job bypasses this Python logic.

The issue is in templates/migrations-job.yaml line 77:

value: postgresql://{{ .Values.postgresql.auth.username }}:{{ .Values.postgresql.auth.password }}@{{ .Release.Name }}-postgresql/{{ .Values.postgresql.auth.database }}

Relevant log output

prisma:warn Prisma doesn't know which engines to download for the Linux distro "wolfi"...
Error: P1013: The provided database string is invalid. invalid port number in database URL.

What part of LiteLLM is this about?

Proxy

LiteLLM version

v1.82.3-stable

Twitter / LinkedIn details

No response