Use consistent naming for variable types
This commit is contained in:
parent
5db3c95954
commit
ebbd6180b9
@ -124,7 +124,7 @@ each category, the available options are alphabetized and described.
|
|||||||
regardless of success. "on_success" requests that the VM only be cleaned up if an
|
regardless of success. "on_success" requests that the VM only be cleaned up if an
|
||||||
artifact was produced. The latter is useful for debugging templates that fail.
|
artifact was produced. The latter is useful for debugging templates that fail.
|
||||||
|
|
||||||
* `network_names` (list) - A list of networks identified by their name label which
|
* `network_names` (array of strings) - A list of networks identified by their name label which
|
||||||
will be used for the VM during creation. The first network will correspond to the VM's
|
will be used for the VM during creation. The first network will correspond to the VM's
|
||||||
first network interface (VIF), the second will corespond to the second VIF and so on.
|
first network interface (VIF), the second will corespond to the second VIF and so on.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user