Open pmahindrakar-oss opened 3 years ago
Commenting on the under review items
parse-proto
is something I use all the time, but it's mainly useful to us as people debugging issues with Flyte executions or task/lp/wf setup. In the ideal world, this command isn't necessary because nothing ever goes wrong. I'd personally like to have it in flytectl
but without the need to specify the proto class. Ideally it'd somehow automatically detect the correct protobuf object to use.get-active-launch-plan
this is useful for users, we should have this.setup-config
this is definitely something we should have, but it collides a bit with @cosmicBboy's project around starting a new flytekit-python project? Or perhaps this is what that will call?get-child-executions
this is important, but may be done automatically depending on the flytectl ux. What's the current behavior for showing launch plan nodes?cc @EngHabu and @kumare3
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 close the issue if we detect no activity in the next 7 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! π
we should implement a few commands, this is great-first-issue for contributors
but we should split it into different issues in an epic - cc @eapolinario
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! π
Describe the feature/command for flytectl The following lists the commands available in flyte-cli and status wrt porting over to flytectl.
Note: I wasn't able to use table format so excuse the long listing. github is yet to support persisting the checkbox state in table markdowns https://stackoverflow.com/questions/66560651/checkbox-in-github-markdown-table-not-updating (https://github.github.com/gfm/#task-list-items-extension-)
parse-proto
Status
list-task-names
Status
list-task-versions
Status
get-task
Status
launch-task
Status
list-workflow-names
Status
list-workflow-versions
Status
get-workflow
Status
list-launch-plan-names
Status
list-active-launch-plans
Status
list-launch-plan-versions
Status
get-launch-plan
Status
get-active-launch-plan
Status
update-launch-plan
Status
execute-launch-plan
Status
watch-execution
Status
relaunch-execution
Status
terminate-execution
Status
list-executions
Status
get-execution
Status
get-child-executions
Status
register-project
Status
list-projects
Status
archive-project
Status
activate-project
Status
register-files
Status
fast-register-files
Status
update-workflow-meta
Status
update-task-meta
Status
update-launch-plan-meta
Status
update-cluster-resource-attributes
Status
update-execution-queue-attributes
Status
update-execution-cluster-label
Status
update-plugin-override
Status
get-matching-attributes
Status
list-matching-attributes
Status
setup-config
Status
Type
Provide a possible output or ux example A clear and concise description of what you want to happen or achieve.