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

Release v0.1.7

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-11 02:34:58 +02:00
parent cd7cc674c7
commit 0ca9bd793c
5 changed files with 21 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/TENANCY_MODULE_BOUNDARY.md
View File

@@ -28,6 +28,13 @@ Tenant lifecycle planning uses registered tenant summary providers and delete
veto providers. Modules that own tenant-scoped data must contribute summaries
so destructive deletion cannot silently miss their rows.
Delete veto providers are registered through module manifests and receive
`(session, tenant_id, resource_id)`. Providers should return a structured
`DeleteVetoIssue`, a list of issues, or `None`; legacy providers that raise an
exception are treated as blocking module vetoes. Tenancy exposes those issues in
the deletion plan with module attribution and resource details, so operators can
see which module blocks or qualifies the lifecycle action.
## Lifecycle Events
`govoplan-tenancy.backend.lifecycle` is the module-local contract for tenant