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.

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

Mention the possibility to specify a URL via SCENARIO_DEF…S_YAML_FILE #5855

Merged
merged 1 commit into from
Aug 14, 2024
Merged
Changes from all commits
Commits
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
5 changes: 4 additions & 1 deletion docs/UsersGuide.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -1179,7 +1179,10 @@ instance.

If the YAML document already exists on the openQA host, you can also use
`SCENARIO_DEFINITIONS_YAML_FILE` which expects the file path of the YAML document
on the openQA host.
on the openQA host. One can also specify an HTTP/HTTPs URL via that variable
when `async=1` is used (see
<<UsersGuide.asciidoc#_spawning_multiple_jobs_based_on_templates_isos_post>>
for details). Then this file is downloaded by the openQA host.

The YAML document itself should define at least one product, machine and job
template like this:
Expand Down
Loading