refactor(frontier): deprecate redundant request parameters from subscription RPC #435
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_idandorg_idparameters in Frontier subscription RPCs while maintaining full backward compatibility.Changes
billing_idas deprecated in all 5 subscription request messages (List, Get, Update, Cancel, Change)org_idas deprecated in Get, Update, Cancel, and Change subscription requestsorg_idin ListSubscriptions as the primary filter parameterignore_empty: trueBackward Compatibility
✅ No breaking changes - All existing clients continue to work:
ignore_empty: trueto allow gradual migrationRationale
Each organization has exactly one billing account. The backend can infer:
billing_idfromorg_id(for ListSubscriptions)billing_idandorg_idfromsubscription_id(for Get/Update/Cancel/Change)This simplifies the API and improves security by preventing clients from passing arbitrary billing IDs.
Related
Backend implementation: Frontier PR link