fix(docs): correct budget_limits key names in OpenAPI docstrings - #33049
fix(docs): correct budget_limits key names in OpenAPI docstrings#33049gautamkishore wants to merge 2 commits into
Conversation
Greptile SummaryThis PR fixes incorrect key names in
Confidence Score: 5/5Documentation-only change correcting docstring examples to match the actual Pydantic model — no runtime behavior is modified. All six changed lines are docstring prose. The replacement key names (max_budget, budget_duration) match the BudgetLimitEntry model exactly, and no logic, validation, or tests are touched. No files require special attention.
|
| Filename | Overview |
|---|---|
| litellm/proxy/management_endpoints/internal_user_endpoints.py | Corrects two budget_limits docstring examples (new_user and user_update) from budget_limit/time_period to max_budget/budget_duration, matching the BudgetLimitEntry model. |
| litellm/proxy/management_endpoints/key_management_endpoints.py | Corrects two budget_limits docstring examples (generate_key_fn and update_key_fn) from budget_limit/time_period to max_budget/budget_duration. |
| litellm/proxy/management_endpoints/team_endpoints.py | Corrects two budget_limits docstring examples (new_team and update_team) from budget_limit/time_period to max_budget/budget_duration. |
Reviews (1): Last reviewed commit: "fix docs: correct budget_limits key name..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Fixes #32695
The OpenAPI docstrings for
budget_limitsin key, team, and user management endpoints used incorrect key names (budget_limit/time_period). The actual API expectsmax_budgetandbudget_duration.Updated 6 occurrences across 3 files to match the actual API schema.