-
Improvement
-
Resolution: Duplicate
-
Neutral
-
None
-
1.1.x
-
None
-
None
-
-
Empty show more show less
If the migration failed or stop in the middle, it must be possible to re-run the migration from this half-migrated repository. In other words it means that if you run a second time a process (like Update Primary Type) on a configuration, it should no break, it just should do nothing because everything is already in a good state.
Here listed all the processes / script that modify the configuration, we must check that if we run one of those a second time on the same piece of config nothing change and nothing break:
- PathChangesImpactingID
- TemplatesAndParagraphsToPagesAndComponents
- RenameDialogsAndChangeInDialogsMap
- PreProcessSTKTemplates
- TransformSTKTemplates
- TransformSimpleTemplates
- MigrateTemplateScripts (it can be disable)
- UpdateExtends (OK)
- UpdateWebsitePrimaryType (OK)
- UpdateMetaDataTemplateId (OK)
- TransformSTKWebsites (OK)
- RemoveTemplateToPrototypeRedundancy
- RemoveClassFromSTKSiteThemes
- TransformExtends
- ExtraSTKTasks
- ExtraFormTasks
- ExtraShopTasks
- ResourcesExtraTasks
- PURExtraTasks
- ChangeReferencesToExtends
- PostMigrationProcessing
Acceptance criteria
- is duplicated by
-
MGNLMIGRATION-168 migration tool page: a button to run or re-run migration of template scripts
- Closed