Uploaded image for project: 'Indy Node'
  1. Indy Node
  2. INDY-925

Implement client migration for rebranding and multiple pool networks support upgrade

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Complete
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Epic Link:
    • Sprint:
      INDY 17.21, INDY 17.22, INDY 17.23

      Description

      When CLI is being started for the first time (per user) after the rebranding upgrade the migration mechanism must check whether the current user's home directory contains .sovrin subdirectory. If the user's home directory contain .sovrin subdirectory, then the migration mechanism must offer the user to migrate this data. If the user agrees then the application data must be migrated from .sovrin subdirectory to .indy subdirectory and the former must be kept as a backup.

      See comments to INDY-830 for details on migration for client.

      UPD:
      In scope of this task a client migration for the indy-node version that supports multiple pool networks (see INDY-832, INDY-833 for details) must also be implemented. This client migration may be combined with the client migration for the rebranded indy-node version (because both rebranding and multiple pool networks support will be introduced simultaneously in the upcoming stable indy-node version).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              VladimirWork Vladimir Shishkin
              Reporter:
              spivachuk Nikita Spivachuk
              Watchers:
              Alexander Shcherbakov, Kelly Wilson, Mike Bailey, Nikita Spivachuk, Vladimir Shishkin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: