Flagsmith / Flagsmith/flagsmith
Remove legacy in-app overage billing
- Dominant language
- Python
- Stars
- 6.6k
- Forks
- 567
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 124
Description
Blocked on https://github.com/Flagsmith/flagsmith/issues/7970
Once we GA the Metered Billing integration, we can remove the legacy in-app overage billing.
This retires the [`charge_for_api_call_count_overages`](https://github.com/Flagsmith/flagsmith/blob/a7b0d217f714d4c59ae78023b3d7147d6c5da095/api/organisations/tasks.py#L159) chain and the 100K-addon quantity billing it drives.
## Acceptance criteria
- [ ] Flagsmith no longer computes or manages overage charges.
- The model `OrganisationAPIBilling` is sunset.
- The task `charge_for_api_call_count_overages` is retired.
- [ ] The `chargebee_metered_billing` feature flag is retired.
Contributor guide
Research direction
Start by reviewing blocked issue 7970 and the legacy chain in api/organisations/tasks.py, including charge_for_api_call_count_overages. Trace references to OrganisationAPIBilling, the 100K-addon quantity billing, and the chargebee_metered_billing feature flag. Done means the model, task, and flag are retired and Flagsmith no longer computes or manages overage charges.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- payments
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100