Tom Klein
07/24/2022, 4:39 PMAnna Geller
07/24/2022, 5:30 PMTom Klein
07/24/2022, 5:32 PMAnna Geller
07/24/2022, 8:41 PMWhy would Prefect not be suitable for that?the description of the desired state led me to believe you may be looking into Infrastructure as Code
Tom Klein
07/24/2022, 11:00 PMSKIP
in the validation task, it would cause all downstream tasks to skip too (and the flow itself, ultimately) - which achieves the goal i wanted, I'm just not sure how "correct" it is as far as best-practices go (e.g. would i have been better of with a conditional flow (i.e. case
) ? the problem with that is that i don't actually have anything to do if the condition is False
for example, only if it's True
)
for the second part -- i'm still unsure if having two "distinct" run-schedules (one for "green" and one for "blue") for the same flow make sense
in an ideal world i would represent the entire schedule of what state should the DB be in at any given moment with like consecutive intervals that are represented in some compact way (and lives inside the flow itself) ---- rather than as just "cron-based schedules for change operations to run in" ---
that way the flow could be run arbitrarily often and simply "adjust" the DB to the correct state when time fits the desired "mapping" (or, when other unique conditions apply -- perhaps) - if the DB doesn't happen to be in the desired state already
kind of like polling behaviorAnna Geller
07/25/2022, 3:55 PMTom Klein
07/25/2022, 3:59 PMAnna Geller
07/25/2022, 4:00 PMTom Klein
07/25/2022, 8:39 PMAnna Geller
07/26/2022, 12:44 PM