Comments (7)
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
a) script
b) Containers
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
"https://argo-workflows.readthedocs.io/en/latest/walk-through/scripts-and-results/" and
"https://argo-workflows.readthedocs.io/en/latest/walk-through/output-parameters/",
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
from argo-workflows.
Ah I see what you mean, since "Scripts and Results" introduces result
but does not really explain it... it's explained in the next page in "Output Parameters". Thanks for elaborating.
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.
from argo-workflows.
Hi. I think you're trying to create a pull request. See this documentation for how.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
I'm aware of your slack message, so if you're stuck reach out there and Tim (who already replied) or I can help
from argo-workflows.
There is an example of this already: https://argo-workflows.readthedocs.io/en/latest/walk-through/scripts-and-results/
Did that not suffice?
from argo-workflows.
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
from argo-workflows.
script
is basically just short-hand for a variant that uses a container
.
Your titles and descriptions also don't mention needing to use container
vs. script
, they only mention using result
, for which there is a page for already.
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 script
is effectively short-hand.
from argo-workflows.
we might actually want to move that section from "Output Parameters" and into "Scripts and Results" instead, and then your example can go there
Please let me know if you want me to make these or any other changes as well. thx
from argo-workflows.
Related Issues (20)
- Ability to override pod GC strategy on a per-template basis HOT 1
- workflows.argoproj.io/completed is false when output set for resource creation HOT 2
- Argo controller cannot find completed pod after seeing the pod as completed, reports workflow as an Error HOT 1
- option to not auto-add tolerations HOT 3
- reduce pod definition size HOT 1
- 3.5 Pagination in workflow list page not working HOT 5
- Dependency between CronWorkflows HOT 5
- 3.5.6+ `items.status.nodes` disappeared from `/api/v1/workflows` endpoint for completed Workflows HOT 5
- Specify external artifacts repo with azure blob HOT 1
- DOM text reinterpreted as HTML in `workflow-logs-viewer.tsx` HOT 2
- Fix incorrect conversion between integer types in `parametrizable.go` HOT 1
- Possible clear-text logging of sensitive information in CLI `token.go` HOT 2
- Archived workflows deletion with GC stopped working after move to namespace install HOT 6
- Devcontainer `Permission denied` error during `chown`
- Unable to run Controller locally on Arm mac M1 HOT 1
- UI: Open custom `links` in new tab or with router navigation depending on address HOT 1
- Argo Workflow MetricsError: Custom Metrics Unable to Resolve Output variables HOT 1
- support `retryPolicy` combination HOT 2
- `podSpecPatch` not applied when configured in `workflowDefaults` and workflow is submitted from template HOT 1
- `podSpecPatch` doesn't evaluate expression when defined at workflow spec HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from argo-workflows.