Case migration - #809
Draft
Klaas-Ritense wants to merge 58 commits into
Draft
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
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true✨ 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 |
# Conflicts: # backend/process-document/src/main/java/com/ritense/processdocument/service/impl/OperatonProcessJsonSchemaDocumentAuditService.java # frontend/projects/valtimo/process/src/lib/models/process.model.ts # frontend/projects/valtimo/shared/assets/core/en.json # frontend/projects/valtimo/shared/assets/core/nl.json
Nightly maintenance run. - backend/case/src/test/kotlin/com/ritense/document/domain/EveritSchemaResolvableOptionsTest.kt:177 — `should stop collecting options beyond the maximum schema depth` built its 121-level fixture as JSON and loaded it through JsonSchema.fromString, which validates the document against the draft-07 meta-schema. That validation recurses per level and overflowed the stack on CI before the walker under test ran. The fixture is now built with the everit builders; the assertion is unchanged.
# Conflicts: # backend/core/src/main/resources/config/liquibase/13-42-0/13-42-0-master.xml # frontend/package-lock.json
Nightly maintenance run.
# Conflicts: # documentation/release-notes/13.x.x/13.43.0/README.md
# Conflicts: # backend/case/src/test/kotlin/com/ritense/document/domain/EveritSchemaGetPropertyTest.kt # documentation/SUMMARY.md # documentation/features/case/for-developers/README.md # documentation/release-notes/13.x.x/13.43.0/README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.