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

ContractService.syncContractByOrgId does not operate on contracts not yet in swatch DB

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • True

      As a swatch engineer, when a contract is not synced properly via UMB messages, I'd like to be able to use the syncContractByOrgId endpoint to correct this.

      Done:

      • syncContractByOrgId should sync all contracts, irrespective of whether the contract is already in the swatch database.

      Testing:

      • Given a contract that exists in the API response from Partner Gateway and does not exist in the swatch DB, calling the syncContractByOrgId endpoint should cause the contract to be added to the swatch database. The contract should be represented in the subscription table API, and should be useable for billable usage remittance calculation as well as sending remittance to AWS.

              karshah@redhat.com Kartik Shah
              khowell@redhat.com Kevin Howell
              Aurobinda Nayak Aurobinda Nayak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: