Agent Refund Decommission

Background

To improve code quality, we plan to move Payment To Customer service (PAYPTC) out of backend-monorepo. However, as some legacy services and reporting still used to read from AgentRefund data, PTC still has to maintain AgentRefund by double writing to it, and this prevents us to clean PAYPTC dependencies. Now we’re planning to decommission AgentRefund data and stop double write. This will impact the information integrity if your service still read or write agentRefund data.

When is the Decommission Date?

We’re planning to stop double write to agent refund on February 24th, 2020

Why is it necessary?

AgentRefund is unmaintained legacy codes
To prepare for TAP decommission as well

Am I affected?

Yes, If your service read or write agentRefund data.
Here are some of the affected modules for agent refund decommission found in backend-monorepo (from Intellij Idea’s backward dependency analysis): https://docs.google.com/spreadsheets/d/1leh3ldutlEBS97OYRT-zTJ-rpfmkLmIZD9MTR4TSrQo/edit?usp=sharing

What do I need to do?

Help us to fill the usage and PIC list in the sheet above to help us have better visibility and coordination
We need your help to redirect your service to read from PTC if it still read from agentRefund data.
If you use AgentRefund for another use case, please notify us! Currently, we have no visibility other than bookingDetail...

For more information, please check the google doc: https://docs.google.com/document/d/1v48DLD4QZqT9N2SAvvaC6eG9keN4brD53ZISosxXFYY/edit#