Fprgrfd stack decommission

Background
FPRGRFD stack is one of the legacy service, shared service & database used in Traveloka.

Currently, fprgrfd-app is used by multiple products to serve old refund feature. The database are occupied primarily by refund data of products which are launched from 2017 (flight, accommodation, train, connectivity, experience, car rental, and airport transport).

IPI team has been introduced the new general refund flow that live in IPI stack. All products which need refund feature already implemented the refund feature with the new flow.

Impacted Services
We have identified the clients of fprgrfd-app:

acdbds (having issue in connectivity)
aprbap
acdbops
aprafop
cultool (hotfix on Monday, May 24)
fpraff :check_green:
fprcis :check_green:
fprpapi (hotfix on Monday, May 24)
fprpf :check_green:
fprrs :check_green:
pprops :check_green:
ppsops :check_green:
trpiapi (hotfix on Monday, May 24)
trppops (release on Monday, May 24)
xpetool (blocked by xpe team)

Please share the security group ID of your service both staging & production by end of May 12, 2021. We will grant the ingress rule from each of services above to ipiprf lbint.
Before releasing the service, you might want to test the connection first in SSM:

Staging: nc -vz ipiprf.ipi.stg-tvlk.cloud 443
Production: nc -vz ipiprf.ipi.tvlk.cloud 443

What do you need to do?
You will need to change old method in fprgrfd to use new method in IPIPRF by following the guideline.

Once your service is released, kindly inform us so we can add tag your service in the list.
Deadline
May 21, 2021

Decommission Timeline

Inform security group of service until May 12, 2021
Ensure all product services has been used IPIPRF & Release until May 21, 2021
Ensure all product use IPITOOL to submit refund internally until May 29, 2021
FPRGRFD-POSTGRES migration to IPI stack on W1 June
FPRGRFD stack will be decommissioned on W2 June

If you have any questions/concerns, please contact @nurlinasetyawan.
Thank you!