TV Instances Staging Termination
Background
TV is shared legacy infra that currently host various implementations with various purposes (such as API, Controller, and Service). and currently, it's also hosting the redirection process NGINX for host-name api-shared-stg.test.tvlk.cloud.
When will it be decommissioned?
TV shared-stg instance will be terminated by Monday, August 3 2020.
Why it is going to be decommissioned?
Since all of the implementation inside TV already migrate to each related service, TV instances only work as redirection now for host-name api-shared-stg.test.tvlk.cloud which is harmful as legacy shared infrastructure.
What do you need to do ?
Migrate your endpoint from api-shared-stg.test.tvlk.cloud to your existing host :
- FE Task, if the code of the host that provide the endpoint still hardcoded with api-shared-stg.test.tvlk.cloud (choose between one of these option) :
- Migrate the implementation of accessing BE endpoint to staging-config (refer to staging-config.test.tvlk.cloud )
- [Optional but not recommended] Change the hard-coded endpoint to the new host-name.
- BE Task :
- [If there is FE Task] Provide the new host that will replace api-shared-stg.test.tvlk.cloud . for example : api-shared-stg-trpiapi.test.tvlk.cloud for post-booking API.
- Change
*Router.config for dev, stg Java Config to the new host.
- [If Staging Config is used] ask @web-infra to change shared-stg.json to the new host.
- Fill the ETA of the migration for tracking https://docs.google.com/spreadsheets/d/1conPp-IzkZY4UeZGwzlhHueteeKsW6ZcKaOWrCHfGjo/edit?usp=sharing , to make sure that the termination plan will be executed according to the plan.
For further inquiry, if you have any question or suggestion you can join #tv-weekly-release and ask @booking-backend-eng. Thank you.