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

Incubation: Support of multiple pool networks by Indy Client (CLI)

    XMLWordPrintable

Details

    • Story
    • Status: Complete
    • Highest
    • Resolution: Done
    • None
    • None
    • None
    • 13, 14, INDY 17.21, INDY 17.22, INDY 17.23, INDY 17.24: Node Perf

    Description

      It should be possible to choose which network to use from the same install of Indy CLI.

      This is important for test networks, private network shards for regulatory reasons, development could use this, and it helps prove Indy can be used independently of Sovrin – reduces open source fork risk.

      It is related to path refactoring in INDY-833

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. INDY-838 Incubation: Check that Indy Node, CLI and SDK can be used on one PC

          • Medium - Has the potential to affect progress.
          • Complete

          Task - A task that needs to be done. INDY-912 Fix documentation: init_indy_node now must be called several time for each desired network

          • Medium - Has the potential to affect progress.
          • Complete
          relates to

          Task - A task that needs to be done. INDY-925 Implement client migration for rebranding and multiple pool networks support upgrade

          • High - Serious problem that could block progress.
          • Complete

          Activity

            People

              VladimirWork Vladimir Shishkin
              gudkov Vyacheslav Gudkov
              Andrey Goncharov, Vladimir Shishkin, Vyacheslav Gudkov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: