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

Ledger upgrade script should accept a package name to update

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Complete
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.6
    • Component/s: None
    • Labels:
      None
    • Documentation Impact:
      Unset

      Description

      Story
      As an administrator of a node on an Indy Network, I want the upgrade transaction to specify my network specific package rather than generic Indy Node so that my network specific package can perform configuration and customization functions such as installing network specific plugins to the Plenum Ledger.

      Acceptance Criteria

      Notes

      • The work to have the upgrade transaction include a value containing the package that should be upgraded is in INDY-1499
      • The Sovrin network wants their network upgrades to call the Sovrin package instead of Indy Node. The Sovrin package depends on Indy Node.
      • There will be a new release of the Sovrin network package with each release of Indy Node.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              esplinr Richard Esplin
              Watchers:
              Richard Esplin
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: