Uploaded image for project: 'RAML Module Builder'
  1. RAML Module Builder
  2. RMB-62

update the upgrade mechanism in rmb

    XMLWordPrintable

Details

    • Core: Platform

    Description

      the idea behind this would be that if the tenant api is called, there will be a check to see if this is a new tenant for this module or whether it is to upgrade the tenant / module - this will be managed by rmb - in that rmb will store in an rmb table (per tenant / per module) - the version of the current module for the tenant - so that if the tenant api is called and there is no table - it will be assumed that this is not an upgrade and the create tenant template sql will be run (as today) - if the table exists the previous and current versions will be passed as variables to the update tenant template sql so that the module can (based on the version) - decide what statements to run in order to upgrade the tenant - this is the same mechanism as today just that the upgrade / version numbers are assumed to be coming from the tenant api request json body (module from , module to

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                shale99 shale99
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases