Skip to content

Case migration - #809

Draft
Klaas-Ritense wants to merge 58 commits into
next-minorfrom
poc/case-migration
Draft

Case migration#809
Klaas-Ritense wants to merge 58 commits into
next-minorfrom
poc/case-migration

Conversation

@Klaas-Ritense

Copy link
Copy Markdown
Member

No description provided.

…& 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
@Klaas-Ritense Klaas-Ritense added the test env Create a remote test environment for this PR in the Ritense product development cluster label Jul 13, 2026
@Klaas-Ritense Klaas-Ritense added test env Create a remote test environment for this PR in the Ritense product development cluster and removed test env Create a remote test environment for this PR in the Ritense product development cluster labels Jul 21, 2026
@github-actions github-actions Bot deleted a comment from valtimo-platform Bot Jul 21, 2026
# Conflicts:
#	backend/case/src/main/kotlin/com/ritense/case/configuration/CaseAutoConfiguration.kt
#	backend/core/src/main/resources/config/liquibase/changelog-master.xml
@Klaas-Ritense Klaas-Ritense added test env Create a remote test environment for this PR in the Ritense product development cluster and removed test env Create a remote test environment for this PR in the Ritense product development cluster labels Jul 22, 2026
@github-actions github-actions Bot deleted a comment from valtimo-platform Bot Jul 22, 2026
@valtimo-platform valtimo-platform deleted a comment from coderabbitai Bot Jul 22, 2026
@Klaas-Ritense Klaas-Ritense removed the test env Create a remote test environment for this PR in the Ritense product development cluster label Jul 22, 2026
@github-actions github-actions Bot deleted a comment from valtimo-platform Bot Jul 22, 2026
@Klaas-Ritense Klaas-Ritense added the test env Create a remote test environment for this PR in the Ritense product development cluster label Jul 22, 2026
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch poc/case-migration

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

# 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
# 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test env Create a remote test environment for this PR in the Ritense product development cluster

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant