Migrating TripDataRetrievalLocalComponent usage

Hello Backend Engineer Fellows,

Currently several of our backend services connect directly to dynamoDB hosting booking context information in tvlk-data aws. This comes with several problems, e.g. :

shared db access with unclear infra vs data ownership
difficult to manage key rotation since a lot of services also needs to be adjusted – which also brings the problem of db credential scattered on multiple domains
the dynamoDB itself is deprecated and planned for decomission in the future since we already have a more proper alternative via BookingCreationContext class. We will follow up at a later time for the details about the decomission plan.

We Need Your Help
If your service currently use / have dependency to TripDataRetrievalLocalComponent / UserDataTrackingContextRetrieval then we need your help to migrate the usage.

The following docs contains the list of usages we have identified in monorepo, along with the migration proposal and guide. Kindly check whether your team are impacted : https://docs.google.com/spreadsheets/d/1pOSVJUYf_slCahMNNC3iagpkLqNSgK-Zwg4YvH9uTnc/edit?usp=sharing

When Is The Time Limit?
The time limit is before the next access key rotation which happens every 3 months. So the next one should be before 11 July 2019. Please ensure your use case has been migrated before then.
Failing to migrate before the timeline will cause your system to lose access to the dynamoDB since the current credential will be revoked after rotation, The new credential will not be exposed outside of trip data systems.

Should you have more questions / concerns please contact us (@tripdata-eng) on #user-eng-channel. Thank you !