add-ideas/govoplan-tenancy
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Use core-owned scope storage

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-10 17:33:43 +02:00
parent 2bc57fefe3
commit 7e8df56723
4 changed files with 17 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -1,9 +1,11 @@
# GovOPlaN Tenancy
`govoplan-tenancy` owns the live `tenancy_tenants` table, tenant lifecycle, and
tenant settings API route contributions during the GovOPlaN module split.
`govoplan-tenancy` owns tenant lifecycle, tenant administration API route
contributions, and the `tenancy.tenantResolver` capability during the GovOPlaN
module split.
`govoplan-access` depends on this module, and core's registry inserts tenancy
before access for authenticated platform composition. Core migrations rename the
historical `tenants` table to the module-prefixed table name for existing
development databases.
`govoplan-access` no longer hard-depends on this module. Access can run in the
single-scope compatibility mode used by the core/access baseline; installing
tenancy adds explicit tenant management and resolver behavior. The shared scope
storage table is core-owned as `core_scopes`; tenancy provides lifecycle and
administration behavior over those rows rather than owning the table.