Uploaded image for project: 'Migration 4.4 to 4.5 (closed)'
  1. Migration 4.4 to 4.5 (closed)
  2. MGNLMIGRATION-166 Add a migration tool page
  3. MGNLMIGRATION-168

migration tool page: a button to run or re-run migration of template scripts

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Fixed
    • Major
    • 1.2.8
    • None
    • None
    • None

    Description

      It is cumbersome (and tacky) to re-trigger the updating code by changing the version in the configuration tree followed by a restart.
      After migration of template scripts, some new areas can be found and these must be added to module configuration.
      Previously, the only way to verify the result was putting the generated Delta tasks (MGNLMIGRATION-164) to VersionHandler of module and restarting the instance.

      This is no longer the case though, because the configuration is updated right away and user
      copies the Delta tasks only after he finds that migration was successful.

      The process:

      1. backup the snapshot of the old configuration and templates
      2. trigger the migration
      3. restore the original from backup or export migrated modules' bootstraps.

      Attachments

        Issue Links

          Activity

            People

              rsiska Robert Šiška
              pbaerfuss Philipp Bärfuss
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: