-
Notifications
You must be signed in to change notification settings - Fork 121
Add support for argo workflow targets #3287
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
base: main
Are you sure you want to change the base?
Changes from all commits
a691d95
611cb3d
3144502
2a26f64
8991fa3
56496f2
db8a65f
fab6221
23f2a0a
bc490a0
1d92786
dfb54e5
a5475da
dc22f71
399d658
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
Add support for argo `Workflow` as targets with an extra option to specify template. |
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Missing user-facing docs for workflow targets. Also, we might want to clarify the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How come workflow targets don't require a copy_target? Since they actually target a specific node of the workflow graph that ends, like a job?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit hesitant in requiring it being copy-target just yet because of the amount of customization included in workflows, Right now we can add support for "catching" a running workflow