Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
True
Epic Link:
billable-usage-retries-status
Git Pull Request:
https://github.com/RedHatInsights/platform-mq/pull/347, https://github.com/RedHatInsights/rhsm-subscriptions/pull/3306, https://github.com/RedHatInsights/rhsm-subscriptions/pull/3376
Intelligence Requested:
Market:

DONE

billable usage components moved from the monolith
Internal APIs for billable usage moved from tally service to new billable usage service
no changes to the queues used or messages being defined
IQE will need to be updated for the paths used for billing usage internal apis. Dev can take a first pass at this in smqe_tools.
Fully remove the usages of the TallySnapshotRepository repository in the BillableUsageController controller. Related to ~~SWATCH-2461~~.

is blocked by

SWATCH-2285 Create billable-usage service & move kstream components to said service

SWATCH-2453 Add the contracts-client module for Quarkus

SWATCH-2460 Move the /internal/rpc/tally/remittance/purge endpoint to the internal billing API

SWATCH-2461 Add new field "totalValueForPeriod" into the billable usage model

mentioned on

(1 mentioned on)

1.	Change reset account for org ID to use the billable usage client	Closed	Jose Carvajal Hilario
2.	Port the purge-remittances cron job from the tally to the billable-usage service	Closed	Jose Carvajal Hilario
3.	Port the process remittance cronjob to the billable usage service	Closed	Jose Carvajal Hilario
4.	Port the tally summary listener from the tally to the billable-usage service	Closed	Jose Carvajal Hilario
5.	Delete all the billable-usage components that have been ported from the tally service	Closed	Jose Carvajal Hilario