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
docs: Add example of a containers step standard output captured in result parameter. #12961
Comments
…er (argoproj#12961) Signed-off-by: Sandeep Khurana <skhurana333@gmail.com>
Hi. I think you're trying to create a pull request. See this documentation for how. I'm aware of your slack message, so if you're stuck reach out there and Tim (who already replied) or I can help |
…er (argoproj#12961) Signed-off-by: Sandeep Khurana <skhurana333@gmail.com>
…put parameter Signed-off-by: Sandeep Khurana <skhurana333@gmail.com>
…er (argoproj#12961) Signed-off-by: Sandeep Khurana <skhurana333@gmail.com>
There is an example of this already: https://argo-workflows.readthedocs.io/en/latest/walk-through/scripts-and-results/ Did that not suffice? |
this example is for step using script. What I am adding is, if step is not using script but outputting a standard output eg using echo |
Your titles and descriptions also don't mention needing to use If we were to add something like that, it would be better to add to the existing "Scripts and Results" page with an explainer that |
ok. Maybe its my lack of understanding. Page - https://argo-workflows.readthedocs.io/en/latest/walk-through/output-parameters/ has section "result output parameter". It has 2 sub sections I am trying to add example under container sub-section. I changed title and description. I think, even if script is short-hand which uses a container, but since there are two separate pages this example may help users who are reading "container" section under "result output parameter on second page. If it does not add much to the doc then please feel free to discard, this issue can be closed as not planned. thx |
Ah I see what you mean, since "Scripts and Results" introduces I can see why that would be confusing... we might actually want to move that section from "Output Parameters" and into "Scripts and Results" instead, and then your example can go there. Let me think about how to organize that better. |
Please let me know if you want me to make these or any other changes as well. thx |
Add one example workflow yaml for showing how the stdout of a container is captured in the result parameter
The text was updated successfully, but these errors were encountered: