You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently (how we think we are going to do it) We can get some pretty big and bloated yaml, The only way to reduce this at this point would be to break stations into their own files and reuse them, but this causes tracking down an issue or seeing the big picture even more difficult. Is there a better way?
Another issue that we ran into is reading and understanding the execution graph, we can show this off in a UI, but when editing the yaml it can be difficult to understand what
Currently (how we think we are going to do it) We can get some pretty big and bloated yaml, The only way to reduce this at this point would be to break stations into their own files and reuse them, but this causes tracking down an issue or seeing the big picture even more difficult. Is there a better way?
Another issue that we ran into is reading and understanding the execution graph, we can show this off in a UI, but when editing the yaml it can be difficult to understand what
one idea was this:
https://gist.github.com/RussellWaite/edf90c253a1a260e7bb00b71144ea85b
Another was to do this:
https://github.com/argoproj/argo-workflows/blob/master/examples/dag-diamond-steps.yaml
The text was updated successfully, but these errors were encountered: