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
When checking the LaunchPlan view:
https://<flyteconsole_url>/console/projects/<project_name>/domains/production/launchPlans/<lp_name>?duration=all
The details list shown doesn't correspond to the latest LaunchPlan registered. In our case it is showing the details from a previous version.
This might be caused because the query to fetch the data seems to be https://<flyteadmin_url>/api/v1/launch_plans/<project_name>/production?filters=eq(launch_plan.name,<project_name>)&token=&limit=1
The issue you're experiencing with Flyteconsole not showing the latest LaunchPlan details is not explicitly covered in the provided data sources. However, your proposed solution to modify the API query to include sorting by created_at in descending order seems reasonable based on general API behavior, though this specific API behavior is not detailed in the sources.
Would you like more detail on how Flyteconsole and FlyteAdmin handle data fetching and display, based on the available information?
Describe the bug
When checking the LaunchPlan view:
https://<flyteconsole_url>/console/projects/<project_name>/domains/production/launchPlans/<lp_name>?duration=all
The details list shown doesn't correspond to the latest LaunchPlan registered. In our case it is showing the details from a previous version.
This might be caused because the query to fetch the data seems to be
https://<flyteadmin_url>/api/v1/launch_plans/<project_name>/production?filters=eq(launch_plan.name,<project_name>)&token=&limit=1
and it might need to be changed to
https://<flyteadmin_url>/api/v1/launch_plans/<project_name>/production?filters=eq(launch_plan.name,<project_name>)&token=&limit=1\&sort_by.direction\=DESCENDING\&sort_by.key\=created_at
Expected behavior
Flyteconsole UI should show the details for the latest LaunchPlan.
Additional context to reproduce
No response
Screenshots
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: