Skip to content
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

Closed
2 tasks done
LeHyperion opened this issue Aug 18, 2023 · 6 comments · Fixed by #5716 · May be fixed by flyteorg/flytectl#418
Closed
2 tasks done

[BUG] Flytectl returns the oldest workflow version when using --latest flag #3972

LeHyperion opened this issue Aug 18, 2023 · 6 comments · Fixed by #5716 · May be fixed by flyteorg/flytectl#418
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@LeHyperion
Copy link

Describe the bug

Description:
When attempting to retrieve the latest version of a workflow using the --latest flag with flytectl 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:

  1. Run the following command:
flytectl get workflow -p MY_PROJECT -d DEV WORKFLOW_NAME --latest
  1. Observe the returned workflow version.

Environment/Configuration:

  • Flytectl version: 0.6.45

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?

  • Yes

Have you read the Code of Conduct?

  • Yes
@LeHyperion LeHyperion added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Aug 18, 2023
@welcome
Copy link

welcome bot commented Aug 18, 2023

Thank you for opening your first issue here! 🛠

@LeHyperion
Copy link
Author

@eapolinario
Copy link
Contributor

@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.

@LeHyperion
Copy link
Author

LeHyperion commented Aug 21, 2023

Hi @eapolinario here is the PR for the fix.
flyteorg/flytectl#418

Copy link

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.
Thank you for your contribution and understanding! 🙏

@RRap0so
Copy link
Contributor

RRap0so commented Sep 3, 2024

@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?

@RRap0so RRap0so removed the stale label Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
3 participants