Nothing measures the storage a member uses, so no storage limit can be offered or enforced #129
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#129
Reference in New Issue
Block a user
What a person cannot do today
Hold an organization to a storage limit, or see how much storage it uses. Half the machinery exists: the wiki farm reports each site's storage bytes and last-modified time and both are recorded on the site row. The entitlements half does not: no storage limit is seeded for any tier, nothing sums the per-site figures per pool, and no consumer compares the two. The storage figures published for each tier are therefore descriptions of an intent, not limits.
What they should be able to do
See storage used against a limit, and have a downgrade say when the lower tier's storage limit is below what the organization already uses, the way the site-count check already does.
Why it matters
A downgrade that silently accepts an over-limit organization leaves the operator carrying storage nobody is paying for and gives the member no signal that anything is wrong.
Where
internal/entitlements, the resource keys and materialization;internal/integrations/fedwiki, the per-site figures already stored; the downgrade check.Done when
A storage resource limit is seeded per tier, per-pool usage is summed from the per-site figures on a schedule, and the downgrade path compares the two and surfaces the over-limit state. Network egress stays out of scope: nothing reports it.
Migrated from status/issues.md at
b7a0e15