AgentRefund Collection Decommission
Why is it necessary?
- It was a legacy that no longer be maintained
- fb-mongod will be decommissioned at October 6th, 2021
What is AgentRefund Collection?
- Mongo collection:
- Cluster Name: fb-mongod
- DB Name: traveloka-agent
- Collection Name: agent.booking.refund2
- PAYPTC module that interact with the collection: legacy-agent-refund (link to s3 of the jar)
Am I affected?
Yes if your service read from or write to AgentRefund collection
What do I need to do?
- Help us to fill the usage and PIC list in the sheet below to help us have better visibility and coordination
- If your service read from the collection, please read from PTC data.
- If your service write to the collection, your service should have been double writing to agent-refund and ptc collection. So you could stop the writing to agent-refund collection.
- We need your help to redirect your service to read from PTC if it still read from agentRefund data. Please use payment-to-customer-* modules to access PTC instead of use legacy-agent-refund module (RefundDataComponent, AgentRefundService, AgentBookingRefundService, etc)
Steps
- List down all services that still read or write to agent-refund.
- List down all use cases per services that need to be altered due to this initiative.
- Updated all affected use cases that read to the collection
- Update all affected use cases.
- Revoke access to the collection.
- Due date: TBD
- Actor: payout eng
- Export / Archive the data for any need later
- Decommission the collection.
- Due date: TBD
- Actor: payout eng
AgentRefund alternative in PaymentToCustomerData
AgentRefund collection:
- Cluster Name: fb-mongod
- DB Name: traveloka-agent
- Collection Name: agent.booking.refund2
PaymentToCustomer collection:
- Cluster Name: fb-mongod
- DB Name: traveloka-agent
- Collection Name: afterSales.payment.to.customer