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

[alerts] Add Windmill Flow to chain together alerts_gcs, comapeo_alerts, and alerts_twilio scripts #67

Open
rudokemper opened this issue Jan 17, 2025 · 0 comments
Assignees
Labels
feature New specs for new behavior

Comments

@rudokemper
Copy link
Member

Feature Request

After #60 and #59 are merged, let's add a Windmill Flow that runs the alerts_gcs, comapeo_alerts, and alerts_twilio scripts in succession.

In doing so, let's optimize each script to provide the right outputs to be picked up by the next script in sequence, and handle outputs from the previous script in sequence. This will likely require some modifications to the logic of each script.

We will want the following behavior:

  • comapeo_alerts only posts alerts if new alerts have been written to the database.1
  • alerts_twilio only sends a request to Twilio to queue a message if new alerts have been written to the database and once comapeo_alerts has been run.

Footnotes

  1. Unless I'm wrong, as of this moment a POST request to the CoMapeo Cloud API will only accept new docId alerts. So if any rows of existing alerts are updated, but the docId stays the same, the CoMapeo API will reject these.

@rudokemper rudokemper added the feature New specs for new behavior label Jan 17, 2025
@rudokemper rudokemper self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New specs for new behavior
Projects
None yet
Development

No branches or pull requests

1 participant