Improving Launchplans and Backfill UX #3333
Replies: 2 comments 2 replies
-
Launch Plans IMO are excellent locations to setup dedicated REST infrastructure. I know we have an undocumented openAPI spec for everything, however a user being able to configure and define something like a fastAPI endpoint (with cors, etc) that could accept arbitrary payloads would be really exciting. |
Beta Was this translation helpful? Give feedback.
-
The existing For the existing
For the backfill features in the UI, it would be great to have some sort of support for these as well.
|
Beta Was this translation helpful? Give feedback.
-
Objective
The objective of this RFC is to improve the UX around launch plans and the ability to perform backfills both programmatically and on the UI. Currently, activating/deactivating launch plans needs to be done with
flytectl
andflytekit.SynchronousClient
. There's no way to do this on the UI. Furthermore, if a user wants to perform a backfill, flyte provides a CLI command,pyflyte backfill
to create an imperative workflow that launches backfill launchplans based on some user-defined time window.The aim of this RFC is to improve the UX around how users interact with launchplans and backfilling workloads.
Beta Was this translation helpful? Give feedback.
All reactions