inbuxa/inbuxa-server
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases 2 Wiki Activity

Multi-tenancy decision before implementation: generated DKIM keys count against maxDkimKeys (MT-17)

Browse Source
This commit is contained in:
jcoffey-dev
2026-09-18 15:28:24 -07:00
parent bcf4a49325
commit 2cbecac415
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/spec/features/multi-tenancy.md
+4
View File
@@ -223,6 +223,10 @@ Each requirement has an ID, and tests name the IDs they check.
emits `limit.tenant-quota`. Moving a domain into a tenant counts its emits `limit.tenant-quota`. Moving a domain into a tenant counts its
principals and keys against the tenant's limits first, and is refused the principals and keys against the tenant's limits first, and is refused the
same way if any limit would be crossed. same way if any limit would be crossed.
**Decision** (2026-09-18): creating a domain with automatic DKIM in a
tenant counts the keys the server will generate for it (MT-9) against
`maxDkimKeys`, and the domain is refused with `overQuota` if they wouldn't
fit. Nothing is ever generated past the limit.
- **MT-18.** Existing objects over a lowered limit stay. Only new ones are - **MT-18.** Existing objects over a lowered limit stay. Only new ones are
refused. refused.
- **MT-19.** Disk quota. `maxDiskQuota` bounds the total storage of every - **MT-19.** Disk quota. `maxDiskQuota` bounds the total storage of every