-
Notifications
You must be signed in to change notification settings - Fork 660
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
[BUG] Flytectl returns the oldest workflow version when using --latest flag #3972
[BUG] Flytectl returns the oldest workflow version when using --latest flag #3972
Comments
Thank you for opening your first issue here! 🛠 |
Should this be |
@LeHyperion , since you already did an initial investigation, can you open a PR? It should be fairly simple to build a local copy of flytectl, just follow https://github.com/flyteorg/flytectl/blob/master/docs/source/contribute.rst. I can help review the change. |
Hi @eapolinario here is the PR for the fix. |
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. |
@eapolinario or @wild-endeavor found this one with the stale label and created a quick PR to get this out. Any chance you could take a looK? |
Describe the bug
Description:
When attempting to retrieve the latest version of a workflow using the
--latest
flag withflytectl get workflow
, I am presented with the oldest version instead of the expected latest version.Expected behavior
Expected Result:
The latest version of the specified workflow should be returned.
Actual Result:
The oldest version of the workflow is returned.
Additional context to reproduce
Steps to Reproduce:
Environment/Configuration:
Additional Notes:
This issue could potentially impact users who rely on fetching the latest version for their operational needs.
Screenshots
No response
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: