Adds --local-files option to EMS/AFD import

[johnclary]

Associated issues

In service of:

• Work with EMS to address spike in Code 3 incidents atd-data-tech#29244

This PR adds a --local-files flag to the AFD/EMS import, fixing an annoyance I've dealt with for a long time, which is that the ETL required you to send an email with an attachment to the S3 inbox—then move that file to the dev inbox— for testing/reprocessing purposes. Now you can simply drop a file in the ./data directory 👍

Testing

URL to test: Local

1. Start your VZ stack

2. Save the dummy data file test.csv in your ./etl/afd_ems_import/data directory.

3. From the ./etl/afd_ems_import directory, run the import using the new --local-files flag:

docker compose run import ems --local-files

4. Now process the email available in the S3 dev inbox:

docker compose run import ems --skip-archive

✅

---

Ship list

• Check migrations for any conflicts with latest migrations in main branch
• Confirm Hasura role permissions for necessary access
• Code reviewed
• Product manager approved

[netlify]

✅ Deploy Preview for vzv-staging canceled.

Name	Link
🔨 Latest commit	1859a59
🔍 Latest deploy log	https://app.netlify.com/projects/vzv-staging/deploys/6a63b6efa221c60008b277a2

[netlify]

✅ Deploy Preview for vze-staging canceled.

Name	Link
🔨 Latest commit	1859a59
🔍 Latest deploy log	https://app.netlify.com/projects/vze-staging/deploys/6a63b6ef91af3500084d6ed7

[mddilley]

Tested locally with and without the csv, and I saw the script process the file (or log that there is no file when there was none). Thanks for adding to the readme! 🚢