Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-3765

audit test coverage to identify any gaps related to step 1 & 2

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None

      Steps 1 & 2 of 

      https://docs.google.com/document/d/1T47CHzl2G5Tye5b7gBCz66q1Up-M-JbgVYmHiHzNdwU/edit?tab=t.0#heading=h.85lyb4xwknnv

       

      Specifically: 

      Step 1: Refactor subscription_measurements to use subscription_number

      The idea is to replace the subscription_id column from subscription_measurements to use the subscription_number instead. The reasons behind this are:

      • We should stop using the subscription ID which is an internal ID from another service
      • We can then add a relationship between the contracts table to the subscription_measurements

      Step 2: Migrate contract_metrics data to subscription_measurements

      Now that the subscription_measurements uses the subscription_number column, we can add a relationship between the contracts table to subscription_measurements, and stop using the contract_metrics. 

       

      The additional advantage is that the subscriptions capacity view will start working as it is (without additional changes) with the contract based products.

              rh-ee-erthomps Eric Thompson
              lburnett0 Lindsey Burnett
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: