Per-workflow quota limiting (blocked on billing team work)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Is your feature request related to a problem?
Right now we allow billing limits on a per product basis, we do not offer granularity over which workflows should be subject to limits
Describe the solution you'd like
We should allow our customers to subject some workflows to billing limits while allowing others to not to be. This is currently blocked by the number of products we have on stripes billing plan
Describe alternatives you've considered
Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points; start by tracing how billing limits are currently applied per product and how workflows map to products. Confirm the Stripe billing-plan constraint with the billing team before defining an implementation, and consider the work complete when selected workflows can be limited independently without exceeding the available product granularity.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100