-
Story
-
Resolution: Done
-
Normal
-
None
-
None
Swatch-producer-aws should update the BillableUsageAggregate being processed with `status`, `error_code` and `billed_on`, and then emit it back to the platform.rhsm-subscriptions.billable-usage.status topic.
Done:
- `GET /internal/remittance/accountRemittances` should reflect the actual status of a given billable usage remittance record.
- Port the logic from swatch-producer-azure around retryAfter (non-fatal billable usage errors should be retried).
- Dev to write a happy path IQE test. Can also extend https://gitlab.cee.redhat.com/insights-qe/iqe-rhsm-subscriptions-plugin/-/blob/master/iqe_rhsm_subscriptions/tests/tally/test_remitance.py?ref_type=heads#L29
- QE should verify the fields for positive and negative test cases. (Specifically testing an inactive sub for the negative case).
- blocks
-
SWATCH-2291 Have swatch-producer-azure emit status
- Closed
-
SWATCH-2611 Update existing billable_usage_remittances status to unknown
- Closed
- depends on
-
SWATCH-2289 Update billable usage when the billable usage component receives notification
- Closed
- is blocked by
-
SWATCH-2503 Adjust GetTotalRemitted calculation to exclude fatal remittance failures
- Closed
- is depended on by
-
SWATCH-2803 Directly handle usages to be retried in the status consumer
- Closed
- mentioned on