Add exit logic to ETL to ensure container stops after completion

[JacobLanter]

I think this should resolve our ETL service not closing after running sometimes. I looked into changing our cron creation command to do a force recreate for our ETL service; however, this will make it recreate immediately, which could interrupt a longer pull of data, which wouldnt break anything since on the next update, it would continue where it left off; however would not be ideal.

[JacobLanter]

Tested this to see if exit handling was the issue, but it didn’t fully resolve the container behavior. After increasing the update interval from 1 min to 5 min, things have been running much more consistently, so it seems more like a timing/start-stop issue with compose up when the interval is too short.

Going to clean up and delete this branch for now, but this is still worth revisiting if we want more near-real-time updates.

[Jalen-Hatcher]

Tested this to see if exit handling was the issue, but it didn’t fully resolve the container behavior. After increasing the update interval from 1 min to 5 min, things have been running much more consistently, so it seems more like a timing/start-stop issue with compose up when the interval is too short.

Going to clean up and delete this branch for now, but this is still worth revisiting if we want more near-real-time updates.

I'm wondering if there's a suitable way to check if we're composing up from another process or if Docker just gets overworked having to compose up multiple times.