-
Notifications
You must be signed in to change notification settings - Fork 120
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Closes #542 Rebases #542 with the generated docs, and opening as myself so that integration tests pass. --------- Signed-off-by: Ahmad Nassri <[email protected]> Co-authored-by: Ahmad Nassri <[email protected]>
- Loading branch information
1 parent
6ffa584
commit 1671c7f
Showing
2 changed files
with
6 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -100,13 +100,13 @@ jobs: | |
merged). To remove all values, set the value to the literal string `{}`. | ||
|
||
If both `env_vars` and `env_vars_file` are specified, the keys in | ||
`env_vars` will take precendence over the keys in `env_vars_files`. | ||
`env_vars` will take precendence over the keys in `env_vars_file`. | ||
|
||
- <a name="env_vars_file"></a><a href="#user-content-env_vars_file"><code>env_vars_file</code></a>: _(Optional)_ Path to a file on disk, relative to the workspace, that defines | ||
environment variables. The file can be newline-separated KEY=VALUE pairs, | ||
JSON, or YAML format. If both `env_vars` and `env_vars_file` are | ||
specified, the keys in env_vars will take precendence over the keys in | ||
env_vars_files. | ||
env_vars_file. | ||
|
||
NAME=person | ||
[email protected]\,[email protected] | ||
|
@@ -115,7 +115,7 @@ jobs: | |
described in `env_vars`. You do not have to escape YAML or JSON. | ||
|
||
If both `env_vars` and `env_vars_file` are specified, the keys in | ||
`env_vars` will take precendence over the keys in `env_vars_files`. | ||
`env_vars` will take precendence over the keys in `env_vars_file`. | ||
|
||
**⚠️ DEPRECATION NOTICE:** This input is deprecated and will be removed in | ||
the next major version release. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -83,7 +83,7 @@ inputs: | |
merged). To remove all values, set the value to the literal string `{}`. | ||
If both `env_vars` and `env_vars_file` are specified, the keys in | ||
`env_vars` will take precendence over the keys in `env_vars_files`. | ||
`env_vars` will take precendence over the keys in `env_vars_file`. | ||
required: false | ||
|
||
env_vars_file: | ||
|
@@ -92,7 +92,7 @@ inputs: | |
environment variables. The file can be newline-separated KEY=VALUE pairs, | ||
JSON, or YAML format. If both `env_vars` and `env_vars_file` are | ||
specified, the keys in env_vars will take precendence over the keys in | ||
env_vars_files. | ||
env_vars_file. | ||
NAME=person | ||
[email protected]\,[email protected] | ||
|
@@ -101,7 +101,7 @@ inputs: | |
described in `env_vars`. You do not have to escape YAML or JSON. | ||
If both `env_vars` and `env_vars_file` are specified, the keys in | ||
`env_vars` will take precendence over the keys in `env_vars_files`. | ||
`env_vars` will take precendence over the keys in `env_vars_file`. | ||
**⚠️ DEPRECATION NOTICE:** This input is deprecated and will be removed in | ||
the next major version release. | ||
|