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

SPIKE - Determine how to avoid migrating existing remittance data while supporting the old and new status flows

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • swatch-billable-usage
    • None

      Investigate approaches to:

      • Support both old and new status flowcharts concurrently.
      • Rollback strategy and conditions if issues arise during the deployment.
      • “Rewrite” relationships with some tables that we only keep around temporarily?
      • Do we need assigned-unassigned statuses or can we use pending for phase 1?
      • Screenshot is attached with the statuses discussion we had in the meeting
      • Would there be a need of out-of-box transaction management that khowell suggested as a workaround?
        • When the billable_usage_aggregate is first created we will be needing to save to db and send to kafka in one transaction

      Done:

      • Document findings on rollback strategies and temporary table use.
      • Provide recommendation on dual-support flow.

              Unassigned Unassigned
              karshah@redhat.com Kartik Shah
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: