-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace calls to performance API with LAMP data (Version 4.1) #976
Conversation
"S3 Headway Fetching": ( | ||
lambda: "2020-11-07T10:33:40" | ||
in json.dumps(data_funcs.headways(date(year=2020, month=11, day=7), ["70061"])) | ||
), | ||
"Performance API Check": ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Briefly read architecture docs, but based on this PR, I'm assuming that LAMP data is held in a separate repo through an s3 bucket? So the S3 Headway Fetching
thats done above covers the check for LAMP as well?
Also why did the MbtaPerformanceAPI need a check but not MbtaAPIV3/V2?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LAMP data is processed through mbta-performance
and stored in s3. We read from s3 here, so yes. That check is sufficient for both
We don't have any checks for the v3 api mostly because we haven't relied on the v3 api for much in the app. Now we only use it to show current accessibility alerts, so we could add a check here, just haven't
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Motivation
Replace all calls to the performance API with LAMP data, and gobble as fallback
Changes
npm update
to do some package cleanup and updatingDepends on
Do not consider merging until we've finished these issues
Testing Instructions
Go to beta, compare results to prod