Skip to content
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

Automate the execution of detecting and flagging failed CR3 downloads #10228

Closed
frankhereford opened this issue Sep 12, 2022 · 2 comments
Closed
Labels
Impact: 4-None Does not affect TPW service delivery Need: 2-Should Have May be painful to leave out, but the solution is still viable Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Service: Dev Infrastructure and engineering Type: DevOps Continuous integration pipeline operations and infrastructure Type: Tech Debt Code or processes that require more work to optimize sustainability, performance, etc. Workgroup: VZ Vision Zero Program

Comments

@frankhereford
Copy link
Member

As per @patrickm02L's request here, this is intends to track the discussion and execution of cron'ing or otherwise automating the query found in the above linked issue. This will cause failed CR3 downloads to be detected and have the crash record set to a state where it will have the CR3 downloaded when a DTS team member next executes that ETL (and provides it with a set of valid cookie values, post-captcha.)

@frankhereford frankhereford added Type: Enhancement Request for an improvement to existing functionality in an application Impact: 4-None Does not affect TPW service delivery Service: Dev Infrastructure and engineering Need: 2-Should Have May be painful to leave out, but the solution is still viable Workgroup: VZ Vision Zero Program Type: DevOps Continuous integration pipeline operations and infrastructure Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Type: Tech Debt Code or processes that require more work to optimize sustainability, performance, etc. Type: Snackoo 🍫 Small straightforward issues or fun bugs and removed Type: Enhancement Request for an improvement to existing functionality in an application labels Sep 12, 2022
@patrickm02L patrickm02L removed their assignment Oct 5, 2022
@patrickm02L
Copy link
Member

patrickm02L commented Nov 29, 2023

Resolved. Refer to Rose's PR 1272

@johnclary johnclary removed the Type: Snackoo 🍫 Small straightforward issues or fun bugs label Mar 4, 2024
@johnclary
Copy link
Member

Lucky for us, we now get CR3s through the CRIS extract, and we don't have a reason to address how this work while we still rely on this legacy process 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact: 4-None Does not affect TPW service delivery Need: 2-Should Have May be painful to leave out, but the solution is still viable Product: Vision Zero Crash Data System Centralize the management of ATD's Vision Zero data Service: Dev Infrastructure and engineering Type: DevOps Continuous integration pipeline operations and infrastructure Type: Tech Debt Code or processes that require more work to optimize sustainability, performance, etc. Workgroup: VZ Vision Zero Program
Projects
None yet
Development

No branches or pull requests

3 participants