-
-
Notifications
You must be signed in to change notification settings - Fork 11.6k
refactor(ptu): give the rollup a source-agnostic deployment record #37501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
yucheng-berri
merged 1 commit into
litellm_internal_staging
from
litellm_lit5809_ptu_deployment_record
Aug 19, 2026
+220
−3
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 New deployment record helper is never used anywhere in the product
A new deployment record type and its builder are added (
_router_deploymentatlitellm/proxy/spend_tracking/ptu_flat_cost_rollup.py:143) with no code anywhere calling them, so the product gains code that never runs while the repository's guidelines ask for the minimum, non-speculative code that solves the problem.Impact: No user-visible behavior change, but unused machinery ships and only tests exercise it, which conflicts with the repo's simplicity rule.
Dead code confirmed by a repo-wide search for callers
_PTUDeploymentand_router_deploymentare referenced only by their own definition and bytests/test_litellm/proxy/spend_tracking/test_ptu_flat_cost_rollup.py. The rollup itself still loads deployments only fromLiteLLM_ProxyModelTable, so the router/config.yaml path this shape exists for is unreachable (the author notes the loader union follows in a later change). CLAUDE.md's "Simplicity First" section states "Nothing speculative", "No features beyond what was asked" and "No abstractions for single-use code".Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.