flowmade-one/architecture
3
0
Fork 0
Code Issues 15 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Add pre-flight verification checklist for data migrations #33

New Issue
Open
opened 2026-01-05 11:59:02 +00:00 by HugoNijhuis · 0 comments
HugoNijhuis commented 2026-01-05 11:59:02 +00:00
Owner
Copy Link

Context

During Gitea storage migration (RWX → RWO), the first migration attempt failed because we didn't verify the rsync completed correctly before switching over.

Problem / Observation

Data migrations are risky operations. The first attempt caused downtime because:

  1. rsync ran without verification
  2. We switched Gitea to the new PVC before confirming data was present
  3. Gitea showed "repository cannot be read" errors

Suggested Improvement

Create a skill or checklist for data migrations that enforces:

  1. Pre-migration: Document what data must exist after migration
  2. Migration: Run copy with verbose logging
  3. Verification: Check specific files/directories exist before proceeding
  4. Cutover: Only switch after verification passes
  5. Rollback plan: Keep old storage until new is confirmed working

Affected Files

  • skills/data-migration/SKILL.md (new)
## Context During Gitea storage migration (RWX → RWO), the first migration attempt failed because we didn't verify the rsync completed correctly before switching over. ## Problem / Observation Data migrations are risky operations. The first attempt caused downtime because: 1. rsync ran without verification 2. We switched Gitea to the new PVC before confirming data was present 3. Gitea showed "repository cannot be read" errors ## Suggested Improvement Create a skill or checklist for data migrations that enforces: 1. **Pre-migration**: Document what data must exist after migration 2. **Migration**: Run copy with verbose logging 3. **Verification**: Check specific files/directories exist before proceeding 4. **Cutover**: Only switch after verification passes 5. **Rollback plan**: Keep old storage until new is confirmed working ## Affected Files - skills/data-migration/SKILL.md (new)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
HugoNijhuis fluxcd-bot renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: flowmade-one/architecture#33
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?