fix(constants): support both CLI_JWT_EXPIRATION_HOURS env var patterns

The constant CLI_JWT_EXPIRATION_HOURS now checks both:
1. CLI_JWT_EXPIRATION_HOURS (without LITELLM_ prefix)
2. LITELLM_CLI_JWT_EXPIRATION_HOURS (with prefix, for backwards compatibility)

This ensures the test_all_numeric_constants_can_be_overridden test passes while maintaining backwards compatibility for users who set LITELLM_CLI_JWT_EXPIRATION_HOURS.
This commit is contained in:
Alexsander Hamir 2026-01-27 12:41:34 -08:00
parent 4a0d63d063
commit 8ac3aa3565

View file

@ -1165,7 +1165,12 @@ LITELLM_CLI_SOURCE_IDENTIFIER = "litellm-cli"
LITELLM_CLI_SESSION_TOKEN_PREFIX = "litellm-session-token"
CLI_SSO_SESSION_CACHE_KEY_PREFIX = "cli_sso_session"
CLI_JWT_TOKEN_NAME = "cli-jwt-token"
CLI_JWT_EXPIRATION_HOURS = int(os.getenv("LITELLM_CLI_JWT_EXPIRATION_HOURS", 24))
# Support both CLI_JWT_EXPIRATION_HOURS and LITELLM_CLI_JWT_EXPIRATION_HOURS for backwards compatibility
CLI_JWT_EXPIRATION_HOURS = int(
os.getenv("CLI_JWT_EXPIRATION_HOURS")
or os.getenv("LITELLM_CLI_JWT_EXPIRATION_HOURS")
or 24
)
########################### DB CRON JOB NAMES ###########################
DB_SPEND_UPDATE_JOB_NAME = "db_spend_update_job"