feat(billing): cap artifact storage per plan - #35
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Cloud metered test results and projects, never bytes. Now that videos and screenshots can be uploaded (#34), a paid workspace could grow storage without bound until retention caught up, and paid tiers keep runs for 90 to 365 days.
Adds a
storageBytesentitlement: free 2 GB, team 50 GB, pro 250 GB, enterprise and self-host unlimited. Usage is a liveSUM(artifact.size)over the org, so expiring runs give the space back.The artifact route reads usage once per upload and uses it twice: probe with a single byte before touching the body (full workspace, 402, nothing streamed), then re-check against the real size after streaming and delete the blob if it crosses. Unlimited tiers skip the query entirely, so self-host never pays for this.
Settings shows used / limit next to the monthly results bar.
Self-host is unaffected:
getEntitlementsreturns unlimited, so no cap and no extra query.