Skip to content

Litellm vanta announcement#24800

Merged
krrish-berri-2 merged 3 commits intomainfrom
litellm_vanta_announcement
Mar 30, 2026
Merged

Litellm vanta announcement#24800
krrish-berri-2 merged 3 commits intomainfrom
litellm_vanta_announcement

Conversation

@krrish-berri-2
Copy link
Copy Markdown
Contributor

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

Delays in PR merge?

If you're seeing a delay in your PR being merged, ping the LiteLLM Team on Slack (#pr-review).

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.
  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
litellm Ready Ready Preview, Comment Mar 30, 2026 4:28pm

Request Review

@CLAassistant
Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@codspeed-hq
Copy link
Copy Markdown
Contributor

codspeed-hq bot commented Mar 30, 2026

Merging this PR will not alter performance

✅ 16 untouched benchmarks


Comparing litellm_vanta_announcement (0128925) with main (5812053)1

Open in CodSpeed

Footnotes

  1. No successful run was found on main (0128925) during the generation of this report, so 5812053 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 30, 2026

Greptile Summary

This PR adds a Vanta compliance blog post (SOC 2 Type 2 / ISO 27001 recertification announcement) along with its image asset, renames Azure environment variables in the setup wizard from AZURE_API_KEY to AZURE_AI_API_KEY, and makes a small formatting fix plus removes the TestFireworksAIChatCompletion test class from the Fireworks AI translation test file.

  • Blog post & image (docs/my-website/blog/vanta_compliance_recertification/): Clean documentation-only addition, no issues.
  • Setup wizard (litellm/setup_wizard.py): The Azure env-var rename (AZURE_API_KEYAZURE_AI_API_KEY, _LITELLM_AZURE_API_BASE__LITELLM_AZURE_AI_API_BASE_) was flagged in a previous review thread for mismatching the naming convention used throughout the rest of the codebase for Azure OpenAI.
  • Test deletion (tests/llm_translation/test_fireworks_ai_translation.py): TestFireworksAIChatCompletion was previously skipped only because of a temporary provider outage. Removing it entirely — rather than re-enabling it or relocating it to an integration-test folder — permanently eliminates the only automated test covering the Fireworks AI chat-completion path (including the test_tool_call_no_arguments regression guard for issue [Bug]: Gemini Tool Call with no arguments raises "function_call missing" exception #6833).

Confidence Score: 3/5

Not safe to merge as-is: permanently deletes test coverage for a core provider path and carries forward the unresolved Azure env-var naming issue.

Two unresolved concerns remain: (1) the TestFireworksAIChatCompletion class is deleted entirely rather than re-enabled or relocated, removing the only chat-completion tests for Fireworks AI including a specific regression guard; (2) the Azure env-var rename (AZURE_AI_API_KEY) was already flagged in the prior review and has not been addressed.

tests/llm_translation/test_fireworks_ai_translation.py (test class removal) and litellm/setup_wizard.py (Azure env-var naming).

Important Files Changed

Filename Overview
tests/llm_translation/test_fireworks_ai_translation.py Removes the entire TestFireworksAIChatCompletion class (previously skipped for an active outage) instead of restoring or relocating it, permanently eliminating chat-completion test coverage for Fireworks AI.
litellm/setup_wizard.py Renames Azure env vars from AZURE_API_KEY/_LITELLM_AZURE_API_BASE_ to AZURE_AI_API_KEY/_LITELLM_AZURE_AI_API_BASE_; previously flagged for potential mismatch with the Azure OpenAI naming convention used elsewhere in the codebase.
docs/my-website/blog/vanta_compliance_recertification/index.md New blog post announcing LiteLLM + Vanta SOC 2 Type 2 and ISO 27001 recertification; documentation-only addition, no issues found.
docs/my-website/static/img/blog/vanta_soc2_recertification.png New static image asset for the Vanta blog post; no issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User runs setup wizard] --> B{Provider selection}
    B -->|Azure OpenAI| C[Prompt for API key\nenv: AZURE_AI_API_KEY]
    B -->|Other providers| D[Prompt for env-specific key]
    C --> E[Prompt for API base URL]
    E --> F[Store in _LITELLM_AZURE_AI_API_BASE_AZURE]
    F --> G[Generate proxy config YAML\napi_base from stored env var]
    G --> H[Write config.yaml]
    D --> H
Loading

Reviews (2): Last reviewed commit: "docs: cleanup image" | Re-trigger Greptile

Comment thread litellm/setup_wizard.py
"name": "Azure OpenAI",
"description": "GPT-4o via Azure",
"env_key": "AZURE_API_KEY",
"env_key": "AZURE_AI_API_KEY",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Env var mismatch: Azure OpenAI vs Azure AI Foundry

The provider here is labelled "Azure OpenAI" (GPT-4o via Azure), whose conventional env var throughout the litellm codebase is the one used in litellm/llms/azure/common_utils.py, litellm/main.py, and litellm/batches/main.py — i.e. the AZURE_*_KEY (without the AI segment).

The AZURE_AI_*_KEY variant (with AI) is specifically for the Azure AI Foundry/Services route and is only used within litellm/llms/azure_ai/.

Changing the wizard's env_key to the AZURE_AI_* name means:

  • The generated YAML will reference the AI-suffixed variable name.
  • Users who have the standard Azure OpenAI key set under the conventional name will have a broken config.
  • It contradicts the naming convention used everywhere else in the repo for Azure OpenAI.

If this is intentionally targeting Azure AI Foundry, please update the provider description and model list accordingly; otherwise revert to the Azure OpenAI variable name.

@krrish-berri-2 krrish-berri-2 temporarily deployed to integration-postgres March 30, 2026 16:26 — with GitHub Actions Inactive
@krrish-berri-2 krrish-berri-2 temporarily deployed to integration-redis-postgres March 30, 2026 16:26 — with GitHub Actions Inactive
@krrish-berri-2 krrish-berri-2 temporarily deployed to integration-postgres March 30, 2026 16:27 — with GitHub Actions Inactive
@krrish-berri-2 krrish-berri-2 temporarily deployed to integration-postgres March 30, 2026 16:27 — with GitHub Actions Inactive
@krrish-berri-2 krrish-berri-2 temporarily deployed to integration-postgres March 30, 2026 16:27 — with GitHub Actions Inactive
@krrish-berri-2 krrish-berri-2 merged commit 1eaf8ed into main Mar 30, 2026
60 of 100 checks passed
@krrish-berri-2 krrish-berri-2 deleted the litellm_vanta_announcement branch March 30, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants