You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: data-migration/README.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,6 +121,7 @@ LOG_LEVEL=info
121
121
SKIP_MISSING_REQUIRED=false
122
122
USE_TRANSACTIONS=true
123
123
CHALLENGE_COUNTERS_ONLY=false
124
+
MIGRATORS_ONLY=
124
125
125
126
# Migration attribution
126
127
CREATED_BY=migration
@@ -136,6 +137,15 @@ Further migration configuration can also be done in `src/config.js`
136
137
137
138
Set `CHALLENGE_COUNTERS_ONLY=true` to re-run the `Challenge` migrator without touching other fields. In this mode the tool will skip normal validations and only update `numOfRegistrants` and `numOfSubmissions` for challenges that already exist in the database. Make sure the JSON payload still includes the challenge `id` and the counter values you want to refresh.
138
139
140
+
### Selecting Specific Migrators
141
+
142
+
Use `MIGRATORS_ONLY` (comma-separated list) to limit which migrators run. The filter matches either the model name or the migrator class name without the `Migrator` suffix. Examples:
143
+
144
+
-`MIGRATORS_ONLY=Challenge` runs the challenge migrator only.
145
+
-`MIGRATORS_ONLY=Challenge,ChallengeType,ChallengeTrack` runs those three migrators.
146
+
147
+
Combine with `CHALLENGE_COUNTERS_ONLY=true` to update just the challenge counters for existing rows.
148
+
139
149
## Testing
140
150
The project includes comprehensive tests to validate that data has been migrated correctly:
0 commit comments