-
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
[FlyteCTL Feature] Archive a specific workflow version #3869
Comments
cc @Future-Outlier would you like to work on it? |
Yes I am interested at it, please give me a chance, thanks a lot kevin and flyte community |
@Future-Outlier , I just assigned this to you. Please let me know if you need help. |
Sure, thanks a lot! |
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. |
@Future-Outlier i don't think this can be done, shall we close this? |
Why? I haven't deep dived into it, but can try it after 5/12(have a talk to give). |
I'll leave my sight after deep diving it, thank you. |
Describe the feature/command for FlyteCTL
Currently,
flytectl update workflow-meta
can only be used to archive an entire workflow (all versions). There is no option to archive a specific version of a workflow.See this slack thread: https://flyte-org.slack.com/archives/CP2HDHKE1/p1689084246507979
Provide a possible output or UX example
We need support for the
--version
flag inflytectl update workflow-meta
: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: