6ed06f974f
VMTasks.dd_load_test appeared as an inheritor of VMTasks.boot_runcommand_delete scenario with hardcoded script to execute. Hardcoded script simplifies both user experience (they do not need to prepare script itself or find it in our samples/source) maintaining (we can ensure that VMTasks.dd_load_test always launchs the latest version of ther script). As like the logic, VMTasks.dd_load_test inherited all the arguments of the parent which is not convinient when we talk about "command" argument. The "command" argument of VMTasks.boot_runcommand_delete is designed to describe what and how the thing should be executed in the VM. For example, the can be just a command or script which should be executed. In VMTasks.dd_load_test we have hardcoded script to execute, so allowing to setup "command" argument can mislead our customers. But anyway, we still need to be able setup some part of it. Despite the fact that we know the interpreter for which our script is written, the VM can be launched from not trivial image which can use alternative interpreter (some variety of /bin/sh like /bin/csh in OpenBSD). So this patch deprecates 'command' argument and replaces it with 'interpreter' (it defaults to /bin/sh). Change-Id: Idbf45c71b66e55ce8eb43a6a913f7bf526712a0b |
||
|---|---|---|
| .. | ||
| boot-runcommand-delete-custom-image.json | ||
| boot-runcommand-delete-custom-image.yaml | ||
| boot-runcommand-delete-script-inline.json | ||
| boot-runcommand-delete-script-inline.yaml | ||
| boot-runcommand-delete-with-disk.json | ||
| boot-runcommand-delete-with-disk.yaml | ||
| boot-runcommand-delete.json | ||
| boot-runcommand-delete.yaml | ||
| dd-load-test.json | ||
| dd-load-test.yaml | ||