[STAGING] CXP Multi-Account New RPC Endpoint

CXP Team is in the middle of migrating AWS Account. We want to migrating the client to use new RPC Endpoint. So, we need your help to release your impacted services to staging.
Please make sure your staging branch contains this commit id:

backend-monorepo: 785232fb48832663c1ab78bf5178cef80b722045 -- https://phabricator.noc.tvlk.cloud/D132994
fpr-product-backend: fa60b0d1c3f69d7c2086d15d81faf241b3cf8a9c -- https://github.com/traveloka/fpr-product-backend/pull/2372

Note: Please change your config files if I miss to change it in your repo.

These the config files which need to be changed:

copsOmnisearchClient-stg.config

Before: hostname: cxpsrch.test.tvlk.cloud | port: 443 | secure: true
After: hostname: cxpsrch-vpce.test.tvlk.cloud | port: 80 | secure: false

copsCrmClient-stg.config

Before: hostname: cxpcrmm.test.tvlk.cloud | port: 443 | secure: true
After: hostname: cxpcrmm-vpce.test.tvlk.cloud | port: 80 | secure: false

copsMessagingClient-stg.config

Before: hostname: cxpmsg.test.tvlk.cloud | port: 443 | secure: true
After: hostname: cxpmsg-vpce.test.tvlk.cloud | port: 80 | secure: false

These the list of impacted services:

usrpapi -> cxpcrmm & cxpmsg
aprpbo  -> cxpcrmm
aprbook -> cxpcrmm
aprbapi -> cxpcrmm
fprbook -> cxpcrmm
fprcio  -> cxpcrmm

ashtool -> cxpsrch
fops    -> cxpsrch
ft      -> cxpsrch
fprtool -> cxpsrch
payod   -> cxpsrch

Due Date
We will terminate old hostname in staging (tvlk-dev) on 20 March 2020.

Feel free to contact me if you have any questions or concerns.
Thank you! :bow: