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
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,7 @@ LOG_LEVEL=info
120
120
# Migration behavior
121
121
SKIP_MISSING_REQUIRED=false
122
122
USE_TRANSACTIONS=true
123
+
CHALLENGE_COUNTERS_ONLY=false
123
124
124
125
# Migration attribution
125
126
CREATED_BY=migration
@@ -130,6 +131,11 @@ Logfiles are by default stored in `logs/migration.log`
130
131
It can be configured using the env variable `LOG_FILE`
131
132
Log levels(increasing level of information): `error`, `warn`, `info`, `debug`
132
133
Further migration configuration can also be done in `src/config.js`
134
+
135
+
### Updating Challenge Counters Only
136
+
137
+
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
+
133
139
## Testing
134
140
The project includes comprehensive tests to validate that data has been migrated correctly:
0 commit comments