[Core feature] Rollbacks and removal of versions of tasks/workflows
Motivation: Why do you think this is important?
Currently I'm setting up CI/CD for my own flyte workflows and have generated in the process some unnecessary versions of tasks. Fortunately this is done in a staging environment so at best these unnecessary versions are just cluttering up the UI right now and at worst staging broke, no big deal.
But say it accidentally was deployed to a production environment and the workflow contained some bug in some task that just breaks everything. It would be great to "undo" the registration/delete or disable the workflow and roll it back to the last working version easily without having to register a new version of a previously working workflow
Related: https://github.com/flyteorg/flyte/issues/5835
Goal: What should the final outcome look like, ideally?
A flytectl remove [workflow] [version] would be great.
Also a UI where I can select a version and delete/disable it.
Describe alternatives you've considered
The current alternative solution is to re-register the last working version as a new version. But this creates clutter imo so is not great.
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
- [x] Yes
Have you read the Code of Conduct?
- [x] Yes
If I understand your concern, you want the ability to remove specific versions of workflows and tasks, correct? We avoided a whole class of errors by deciding to not expose the ability to remove Flyte entities, but would archiving suffice, @cjidboon94?
Currently we only support archiving specific executions and workflows (which affects all versions), but I can totally see a use case for archiving specific versions of named entities.
"Hello 👋, this feature request 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 close the issue if we detect no activity in the next 14 days. Thank you for your contribution and understanding! 🙏"
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏