Right now if you set magnolia.update.stkMigration on true in the magnolia.properties you could trigger the migration of the FTL on startup. This is a bit confusing, could lead to issues and also not recommended by the migration process. For all these reason we must remove this mechanism.

Under certain circumstances, when there is a magnolia.update.stkMigration properties present in any magnolia.properties, the installation of the module will fail with

Could not install or update magnolia-4-5-migration module. Task 'Trigger migration scripts' failed. (IOException: Can't find resource file at /scripts/migration/from4_4To4_5/ConfiguredMigration.groovy)

This is due to the fact that the getExtrasInstallTasks function still references an old file that doesn't exist anymore in the 1.2 version of this module. Looking closer at the whole VH, it should be revised and updated to not even consider the property magnolia.update.stkMigration since this has been removed altogether.