Case migration - #809
Conversation
…& extensible components Add a case migration feature that migrates cases from one case-definition version to the next via *.case-migration.json plans (importer/exporter/auto-deploy). Backend: - contract: MigrationComponentDeployer/Executor bridge so unlinked modules own their plan sections (dataMigration -> case, processMigration -> core) - case: plan skeleton + dataMigration (value-resolver based), triggers with conditions as a per-plan filter, cluster-safe single-runner (lease + fencing token + ShedLock + @Version), crash recovery via scheduler, per-case atomic child table, management CRUD + start/status REST endpoints - core: processMigration component deployer/config + liquibase tables - process-document: processMigration executor (Operaton MigrationPlan, sync) Frontend: - case-management migration tab: plan list, monitoring with polling, start/delete - routed JSON-editor screen for creating/editing plans (tabbed, extensible)
# Conflicts: # backend/apps/dev/src/main/kotlin/com/ritense/gzac/GzacApplication.kt # frontend/package-lock.json
# Conflicts: # frontend/package-lock.json
# Conflicts: # backend/case/src/main/kotlin/com/ritense/case/configuration/CaseAutoConfiguration.kt # backend/core/src/main/resources/config/liquibase/changelog-master.xml
|
Will create a test environment. This comment will be updated once it is available. This usually takes a few minutes.
Test environment metadata:
Observability: |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
No description provided.