You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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. ↩
The text was updated successfully, but these errors were encountered:
Feature Request
After #60 and #59 are merged, let's add a Windmill Flow that runs the
alerts_gcs
,comapeo_alerts
, andalerts_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.1alerts_twilio
only sends a request to Twilio to queue a message if new alerts have been written to the database and oncecomapeo_alerts
has been run.Footnotes
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 thedocId
stays the same, the CoMapeo API will reject these. ↩The text was updated successfully, but these errors were encountered: