-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
-
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.
- blocks
-
SWATCH-1937 Refactor contract ingestion to increase consistency and testability
- Closed