Implement tenant isolation for Entries Service: switch transaction handling to tenantTransaction, introduce Flyway-based migrations for tenant schemas, and add JdbcTenantRegistry with control schema support. Include migration tests, schema initializations, and E2E tenant isolation. Update configuration and roadmap with completed A-1 tasks.
This commit is contained in:
@@ -17,9 +17,23 @@ spring:
|
||||
health-check-path: /actuator/health
|
||||
health-check-interval: 10s
|
||||
|
||||
flyway:
|
||||
enabled: ${SPRING_FLYWAY_ENABLED:true}
|
||||
# Control-Schema Migrationen (Registry)
|
||||
locations: classpath:db/control
|
||||
# Default-Schema für Control-Registry
|
||||
schemas: control
|
||||
|
||||
server:
|
||||
port: ${SERVER_PORT:${ENTRIES_SERVICE_PORT:8083}}
|
||||
|
||||
# Multitenancy Bootstrap (temporär): Liste erlaubter Schemas (kommagetrennt)
|
||||
multitenancy:
|
||||
defaultSchemas: ${MULTITENANCY_DEFAULT_SCHEMAS:public}
|
||||
# Umschalten zwischen in-memory (bootstrap) und jdbc (produktiv)
|
||||
registry:
|
||||
type: ${MULTITENANCY_REGISTRY_TYPE:jdbc} # jdbc | inmem
|
||||
|
||||
management:
|
||||
endpoints:
|
||||
web:
|
||||
|
||||
Reference in New Issue
Block a user