-
Notifications
You must be signed in to change notification settings - Fork 89
Move contents of new_etl
to parent directory, replacing the old ETL implementation
#1219
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
Conversation
We no longer run diff backup jobs since we no longer use postgres, and our slack error reporting has changed significantly, so we're going to delete our current test module and have an issue filed to write new tests.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Note that the diffs for this PR are pretty wacky. I'd suggest reviewing by commit to get a sense of what changed and how. What I basically did was: |
This looks good to me, thanks! Did the change you added to parse for the correct Shapefile in |
It addressed the issue with the unit tests (which is also what I posted to Slack), but it didn't totally solve the issue park_priority issue
|
Checklist:
Before submitting your PR, please confirm that you have done the following:
staging
branch, NOT againstmain
Description
Since #1212 was merged, we now have a new version of the pipeline that we plan to use to generate our data that powers the website. With that in mind, this PR "promotes" what we were calling the
new_etl
to the parent directory, replacing the old implementation.To get the unit tests to run, I also had to make a few small tweaks in 31fa06d and 8459c41.
In a follow up PR, I plan to continue removing dead code and outdated documentation (mostly anything that relates to Postgres).
Related Issue(s)
This PR addresses issue #...
How Has This Been Tested?
Our (minimal) unit tests pass, linting and formatting passes, and the new ETL at least runs. It doesn't run to completion, however, as I encountered an issue at this step:
Details
but this indicates a part of the pipeline we need to fix, not an error with the file moving itself.