-
Notifications
You must be signed in to change notification settings - Fork 690
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
[Feature] [flytekit] FlyteRemote listing of workflows and launch plans #1394
Labels
backlogged
For internal use. Reserved for contributor team workflow.
Comments
8 tasks
45 tasks
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation: Why do you think this is important?
This issue is a continuation of #1290. That PR only provided for the listing of tasks and executions.
The reason for this is because of the
promote_from_model
logic forFlyteWorkflow
andFlyteLaunchPlan
.For workflows, when promoting from model, we also need the definition of any launch plan nodes.
For
FlyteLaunchPlan
, fetching implieshttps://github.com/flyteorg/flytekit/blob/b49578b931bf092f7f8ea743abe3ca4a46466f18/flytekit/remote/remote.py#L400-L403
technically also implies the fetching of the underlying workflow for completion's sake.
We can't get all this information today from one Admin call. That means that listing 100 workflows could trigger a whole ton of requests to Admin. This is a separate ticket because we should think about whether there's a better way of doing this.
The text was updated successfully, but these errors were encountered: