Skip to content

Commit 0ea8203

Browse files
docs(platform-migrations): propose a slug-keyed platform migration engine
Platform migrations are identified by a dense integer that also serves as cluster state, so concurrent migration PRs conflict on the next number, a scalar stamp cannot describe a branched history, and the pending set is computed away from the migrations themselves. Replace the integer with a slug as identity and an applied-set ledger: one m.<slug> key per migration in the cozy-system/cozystack-version ConfigMap, carrying state, time, script sha256, batch, image and attempts. What runs is the set difference between what the chart ships and what the ledger records, so a skipped release, a failed run or a deleted script leaves a record instead of a silent gap. Execution order is derived at build time from the release tag trees into a generated, untracked order.d/. Migrations are pre-apply (the blocking Helm hook) or background (serial Jobs run by the operator with capped, backed-off retries). The proposal covers revocation, a retention floor that refuses an upgrade from below it, fresh-install seeding, conversion of the existing integer set through a legacy map, a migration contract with a linter and a generator, the test layers, and the phases of the rollout. Assisted-By: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 93e347a commit 0ea8203

1 file changed

Lines changed: 556 additions & 0 deletions

File tree

  • design-proposals/platform-migrations

0 commit comments

Comments
 (0)