Replies: 2 comments
-
I mentioned in your other discussion but an example Workflow is really useful when asking questions. The issue templates require one, but unfortunately GitHub does not have discussion templates 😕
This sounds like a prime use-case for parametrizing your template. For instance, you could use |
Beta Was this translation helpful? Give feedback.
-
I am not sure if apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: key-only-artifacts-
spec:
entrypoint: main
templates:
- name: main
steps:
- name: generate
template: generate
arguments:
artifacts:
- name: file
s3:
key: my-file-01
- name: generate
template: generate
arguments:
artifacts:
- name: file
s3:
key: my-file-02
- name: generate
container:
image: argoproj/argosay:v2
args: [ echo, hello, /mnt/file ]
outputs:
artifacts:
- name: file
path: /mnt/file
|
Beta Was this translation helpful? Give feedback.
-
I am building a workflow have the form of A -> B -> A -> B -> A -> B
What I hope is, the first time I run step B its output artifact should use the key steps/b/iters/0,
and the second time it should become steps/b/iters/1 and so on.
An idea way is all step B can share the same template and set their own artifact key.
But I am not sure if it is possbile to do so as I don't see any example to config output artifact in Step
Beta Was this translation helpful? Give feedback.
All reactions