docs: Projekt-API in API-Docs, Developer Portal + MKDocs ergaenzen
Some checks failed
CI / go-lint (push) Has been skipped
CI / python-lint (push) Has been skipped
CI / nodejs-lint (push) Has been skipped
CI / test-go-ai-compliance (push) Failing after 38s
CI / test-python-backend-compliance (push) Successful in 1m0s
CI / test-python-document-crawler (push) Successful in 23s
CI / test-python-dsms-gateway (push) Successful in 20s
Some checks failed
CI / go-lint (push) Has been skipped
CI / python-lint (push) Has been skipped
CI / nodejs-lint (push) Has been skipped
CI / test-go-ai-compliance (push) Failing after 38s
CI / test-python-backend-compliance (push) Successful in 1m0s
CI / test-python-document-crawler (push) Successful in 23s
CI / test-python-dsms-gateway (push) Successful in 20s
- endpoints.ts: Neues Modul "Projekte — Multi-Projekt-Verwaltung" (5 Endpoints) - Developer Portal: projectId im Beispiel-Code, Multi-Projekt als Feature - multi-tenancy.md: Verweis auf multi-project.md + neue Tests Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -54,7 +54,14 @@ Der Next.js-Proxy setzt automatisch den `X-Tenant-ID` Header:
|
||||
headers['X-Tenant-ID'] = clientTenantId || process.env.DEFAULT_TENANT_ID || '9282a473-...'
|
||||
```
|
||||
|
||||
## Multi-Projekt pro Tenant
|
||||
|
||||
Seit Migration 039 kann jeder Tenant mehrere Compliance-Projekte anlegen. Jedes Projekt hat einen eigenen SDK-State und eigene Stammdaten (CompanyProfile).
|
||||
|
||||
Details: [Multi-Projekt-Architektur](multi-project.md)
|
||||
|
||||
## Tests
|
||||
|
||||
- 20 Tests in `test_vvt_tenant_isolation.py`
|
||||
- UUID-Validierung, Header-/Query-Precedence, Model-Column-Checks, Route-Isolation
|
||||
- 6 Test-Klassen in `test_project_routes.py` — Projekt-CRUD, Tenant-Isolation, State-Isolation
|
||||
|
||||
Reference in New Issue
Block a user