refactor: deprecate billing_id and project_id in entitlement and usag… #438
Conversation
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
…e RPCs Mark billing_id and project_id fields as deprecated in the following RPCs: - CheckFeatureEntitlement - CreateBillingUsage - RevertBillingUsage The billing_id will now be automatically inferred from org_id on the backend. The project_id is also deprecated - use org_id directly instead. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
rohilsurana
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Deprecate
billing_idandproject_idparameters in entitlement and usage RPCs. These fields will now be automatically inferred fromorg_idon the backend.Changes
Marked the following fields as deprecated:
CheckFeatureEntitlementRequest:billing_id,project_idCreateBillingUsageRequest:billing_id,project_idRevertBillingUsageRequest:billing_id,project_idUsage
Clients should now only provide
org_idwhen calling these RPCs:CheckFeatureEntitlementCreateBillingUsageRevertBillingUsageThe backend will automatically infer the billing account ID from the organization ID.