Is there a way to avoid using vim/vi. Lets say the workflow templates were deployed using argo. Can an operator just change the value of the parameters in template and launch workflow?
This needs to have clearer descriptions and take a bit of time to explain what you're showing. You say "a workflow" is "how you define and use your workflows" and jump around the screen so it's not obvious what is happening. Maybe it can't be shown in 5 minutes, but this video is understandable to those who already use Argo (and therefore need no introduction to the project) and is baffling for those who don't (and who do need an introduction) so it really doesn't have any target audience.
The recursive definition of "a workflow is a workflow" is pretty strange. Usually when you define a word, you don't use that same word (upper vs lower case in specific vs generic notwithstanding) in the definition itself. It's such poor scripting.
You're watching a video on Argo workflows, but can't extrapolate that "magically" just means that it's abstracting artifact transfers between workflow steps to make your life easier?
Presenter: Workflow is how you do a workflow.
Me: Uhhhhh....
seriously, what the fuck is this?
mmmm that keyboard ASMR
I love Argo
How did you got namespace as argo in UI, for me its undefined, i have to edit it manually to get my workflows and templates'
How I can cron AWS glue scripts in ARGO Workflow
👌
Is there a way to avoid using vim/vi. Lets say the workflow templates were deployed using argo. Can an operator just change the value of the parameters in template and launch workflow?
How does it compare with Tekton?
@Roberto Quintanilla ArgoProj also has ArgoCD
ok !!!
uses Vim :D doesn't use the "Home" key :(
Maybe he is on a Mac 😅
@@elael2 CMD+Left Arrow
command/ctrl + a
ctrl+a to go to the beginning of a llne in bash.... you are welcome.
Hard to flow control, not like spark.
Nice video but nothing is understood.
This needs to have clearer descriptions and take a bit of time to explain what you're showing. You say "a workflow" is "how you define and use your workflows" and jump around the screen so it's not obvious what is happening. Maybe it can't be shown in 5 minutes, but this video is understandable to those who already use Argo (and therefore need no introduction to the project) and is baffling for those who don't (and who do need an introduction) so it really doesn't have any target audience.
The recursive definition of "a workflow is a workflow" is pretty strange. Usually when you define a word, you don't use that same word (upper vs lower case in specific vs generic notwithstanding) in the definition itself. It's such poor scripting.
sorry but if you say shit like "magically places the file" why even make the video
You're watching a video on Argo workflows, but can't extrapolate that "magically" just means that it's abstracting artifact transfers between workflow steps to make your life easier?
@@Drawthemoral Are you saying there is no magic in computer science ??? 😢