Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Does anyone know if Flyte scheduler supports setting up start and end dates for schedules? For example, “run every Tuesday for the next two months”? Meaning that the schedule itself will be automatically enabled only during certain period and disabled after that. I have seen that we can use flyte with AWS EventBridge scheduler that allows this, but not sure if this setting is exposed anyhow through the LaunchPlan API. CC <@U06MQ3WEUBS>

We were thinking of implementing this functionality ourselves by creating a scheduler workflow that enables or disables other launchplans by inspecting a custom DB table that will store the start/end time range for each launchplan that should have it. But then realised that AWS EventBridge actually supports this internally, so maybe we can leverage it if we switch to the AWS scheduler in Flyte?

Adding a start and end date is indeed in the roadmap

Got it. Any ways we can work around this now? Or we’ll need custom logic around it for the time being?