Hello fellow backend engineers,

Booking platform team will be doing endpoint migration for trpdata service and related stack in order to decommission legacy non Infra as Code (IaC) resources.

These changes only affects staging environment.

Please check the guide below to know whether your services are affected and how you can migrate

==============================
Services connecting to trpdata via rpc
==============================

1. Your service is hosted on tvlk-dev, code in monorepo
How to migrate :

Cherry pick / ensure these commits are included on your service branch :

ebc57cd23be12e181590edc3c4760f8b6ba87229 (https://phabricator.noc.tvlk.cloud/D127439)
8ad84e682c3410e44675b92594d70b7ed183d031 (https://phabricator.noc.tvlk.cloud/D129535)

change your config for connecting to trpdata

previous : http://trpdata-shared-stg.test.tvlk.cloud:60095
new : https://trpdata.test.tvlk.cloud (don't forget to set secure : true)

3. Your service is hosted on aws multi account (non tvlk-dev)
How to migrate :

Create new / ensure that your VPC Endpoint are already pointing to the correct service name

previous : com.amazonaws.vpce.ap-southeast-1.vpce-svc-03c11c752a12ccfee
new : com.amazonaws.vpce.ap-southeast-1.vpce-svc-06e9cbac37063e46b

If creating a new VPC Endpoint, ensure that your existing SG are attached on the new one
Update the Route 53 / target config in your account / application to use the correct VPC endpoint

=========================================
SQS subscribing to SNS topic : tda-booking-events
=========================================

previous : arn:aws:sns:ap-southeast-1:517530806209:tda-booking-events
new : arn:aws:sns:ap-southeast-1:517530806209:trpdata-booking-events

1. Your SQS resides on tvlk-dev
How to migrate :
i. Reusing existing SQS

ping @tripdata-eng, let us know which one is your subscription, and that you wished to use the same SQS
@tripdata-eng will manually remove subscription to the old topic, and add subscription to the new topic via IaC
Note that this might cause period of either publishing data loss / duplication during the migration

provision your new SQS resource
ping @tripdata-eng, let us know the arn of your new SQS
@tripdata-eng will manually remove subscription to the old topic, and add subscription to the new topic via IaC
Adjust your service to consume from the new SQS

provision your new SQS resource
ping @tripdata-eng, let's discuss. Due to the nature of cross account subscription the steps are a bit more complicated, but still doable.

==============================================
Bonus : SQS-es which are directly being called by trpdata
==============================================
How to migrate :

Currently unaffected, but it will be very appreciated if you migrate into using SNS subscription instead
migration steps is similar with SNS - SQS migration above
There might be publishing event duplicates during the migration period

==========
Due Date
==========
We'll terminate the non IaC resources by 7 Jan 2020.

As usual, ping @tripdata-eng should you have any questions / difficulties.
Thank you !!

Staging Endpoint Migration for trpdata