Added migration for legacy variable config. #939
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Variables refactor (#859) changed the structure of
VariableConfigobjects but didn't include migration for existing experiments, causing them to crash when loading (see #909).Old format (pre-v19):
New format (v19+):
Changes
utils/src/variables.legacy.utils.ts- Migration utilities withmigrateVariableConfig()andmigrateVariableConfigs()utils/src/variables.utils.ts-extractVariablesFromVariableConfigs()now auto-migrates old configs as a runtime fallbackfunctions/src/migrations/migrate-variable-configs.ts- One-time Firestore migration scriptRunning the Migration
Option 1: One-time database migration
For production, set
GOOGLE_APPLICATION_CREDENTIALSor usegcloud auth application-default login.Option 2: Runtime migration (automatic fallback)
Old configs are automatically migrated at runtime when
extractVariablesFromVariableConfigs()is called. This ensures experiments load even if the database migration hasn't been run, but the one-time script may be preferable for a full fix.