Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add documentation how to use parameter-file's #1191

Merged
merged 1 commit into from
Jan 25, 2019
Merged

Add documentation how to use parameter-file's #1191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions examples/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,16 @@ The argo CLI provides a convenient way to override parameters used to invoke the
```sh
argo submit arguments-parameters.yaml -p message="goodbye world"
```
In case of multiple parameters that can be overriten argo CLI provides also command to load whole parameters files in yaml or json format. That files can look like that:

```yaml
message: goodbye world
```

To run use following command:
```sh
argo submit arguments-parameters.yaml --parameter-file params.yaml
```

Command line parameters can also be used to override the default entrypoint and invoke any template in the workflow spec. For example, if you add a new version of the `whalesay` template called `whalesay-caps` but you don't want to change the default entrypoint, you can invoke this from the command line as follows.
```sh
Expand Down