diff --git a/AzurePowershell.Test.targets b/AzurePowershell.Test.targets index a4adcf2014e1..1a0ecf86db9f 100644 --- a/AzurePowershell.Test.targets +++ b/AzurePowershell.Test.targets @@ -66,6 +66,7 @@ + diff --git a/build.proj b/build.proj index 1de7a0a2ce61..0dff01d87f12 100644 --- a/build.proj +++ b/build.proj @@ -137,6 +137,9 @@ + + diff --git a/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js b/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js index bdb825056917..6f5803acbd13 100644 --- a/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js +++ b/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js @@ -283,9 +283,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('virtual-machine-scale-set') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.command('virtual-machine-scale-set') + setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.command('set') .description($('Set virtual-machine-scale-set in config string or files, e.g. \r\n{\r\n "sku":{\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n },\r\n "upgradePolicy":{\r\n "mode":""\r\n },\r\n "virtualMachineProfile":{\r\n "osProfile":{\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "storageProfile":{\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n },\r\n "networkProfile":{\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n },\r\n "extensionProfile":{\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n },\r\n "provisioningState":"",\r\n "id":null,\r\n "name":null,\r\n "type":null,\r\n "location":"",\r\n "tags":{\r\n }\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -419,9 +419,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('virtual-machine-scale-set') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.command('virtual-machine-scale-set') + removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.command('remove') .description($('Remove virtual-machine-scale-set in config string or files, e.g. \r\n{\r\n "sku":{\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n },\r\n "upgradePolicy":{\r\n "mode":""\r\n },\r\n "virtualMachineProfile":{\r\n "osProfile":{\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "storageProfile":{\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n },\r\n "networkProfile":{\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n },\r\n "extensionProfile":{\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n },\r\n "provisioningState":"",\r\n "id":null,\r\n "name":null,\r\n "type":null,\r\n "location":"",\r\n "tags":{\r\n }\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -503,9 +503,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('virtual-machine-scale-set') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.command('virtual-machine-scale-set') + addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.command('add') .description($('Add virtual-machine-scale-set in config string or files, e.g. \r\n{\r\n "sku":{\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n },\r\n "upgradePolicy":{\r\n "mode":""\r\n },\r\n "virtualMachineProfile":{\r\n "osProfile":{\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "storageProfile":{\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n },\r\n "networkProfile":{\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n },\r\n "extensionProfile":{\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n },\r\n "provisioningState":"",\r\n "id":null,\r\n "name":null,\r\n "type":null,\r\n "location":"",\r\n "tags":{\r\n }\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -643,9 +643,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSku0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = parametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = parametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('sku') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSku0.command('sku') + setparametersCreateOrUpdateVirtualMachineScaleSetsSku0.command('set') .description($('Set sku in config string or files, e.g. \r\n {\r\n ...\r\n "sku" : {\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -714,9 +714,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSku1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = parametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = parametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('sku') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1.command('sku') + removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1.command('remove') .description($('Remove sku in config string or files, e.g. \r\n {\r\n ...\r\n "sku" : {\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -768,9 +768,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSku2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = parametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = parametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('sku') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSku2.command('sku') + addparametersCreateOrUpdateVirtualMachineScaleSetsSku2.command('add') .description($('Add sku in config string or files, e.g. \r\n {\r\n ...\r\n "sku" : {\r\n "name":"",\r\n "tier":"",\r\n "capacity":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -843,9 +843,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('upgrade-policy') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.command('upgrade-policy') + setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.command('set') .description($('Set upgrade-policy in config string or files, e.g. \r\n {\r\n ...\r\n "upgradePolicy" : {\r\n "mode":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -891,9 +891,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('upgrade-policy') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.command('upgrade-policy') + removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.command('remove') .description($('Remove upgrade-policy in config string or files, e.g. \r\n {\r\n ...\r\n "upgradePolicy" : {\r\n "mode":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -935,9 +935,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('upgrade-policy') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.command('upgrade-policy') + addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.command('add') .description($('Add upgrade-policy in config string or files, e.g. \r\n {\r\n ...\r\n "upgradePolicy" : {\r\n "mode":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -987,9 +987,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('virtual-machine-profile') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.command('virtual-machine-profile') + removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.command('remove') .description($('Remove virtual-machine-profile in config string or files, e.g. \r\n {\r\n ...\r\n "virtualMachineProfile" : {\r\n "osProfile":{\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "storageProfile":{\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n },\r\n "networkProfile":{\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n },\r\n "extensionProfile":{\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1046,9 +1046,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('virtual-machine-profile') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.command('virtual-machine-profile') + addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.command('add') .description($('Add virtual-machine-profile in config string or files, e.g. \r\n {\r\n ...\r\n "virtualMachineProfile" : {\r\n "osProfile":{\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "storageProfile":{\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n },\r\n "networkProfile":{\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n },\r\n "extensionProfile":{\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1131,9 +1131,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('os-profile') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.command('os-profile') + setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.command('set') .description($('Set os-profile in config string or files, e.g. \r\n {\r\n ...\r\n "osProfile" : {\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1245,9 +1245,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('os-profile') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.command('os-profile') + removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.command('remove') .description($('Remove os-profile in config string or files, e.g. \r\n {\r\n ...\r\n "osProfile" : {\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1319,9 +1319,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('os-profile') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.command('os-profile') + addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.command('add') .description($('Add os-profile in config string or files, e.g. \r\n {\r\n ...\r\n "osProfile" : {\r\n "computerNamePrefix":"",\r\n "adminUsername":"",\r\n "adminPassword":"",\r\n "customData":"",\r\n "windowsConfiguration":{\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n },\r\n "linuxConfiguration":{\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n },\r\n "secrets":[\r\n {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1437,9 +1437,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('windows-configuration') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.command('windows-configuration') + setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.command('set') .description($('Set windows-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "windowsConfiguration" : {\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1531,9 +1531,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('windows-configuration') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.command('windows-configuration') + removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.command('remove') .description($('Remove windows-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "windowsConfiguration" : {\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1595,9 +1595,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('windows-configuration') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.command('windows-configuration') + addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.command('add') .description($('Add windows-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "windowsConfiguration" : {\r\n "provisionVMAgent":null,\r\n "enableAutomaticUpdates":null,\r\n "timeZone":"",\r\n "additionalUnattendContent":[\r\n {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ],\r\n "winRM":{\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1693,9 +1693,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('additional-unattend-content') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.command('additional-unattend-content') + setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.command('set') .description($('Set additional-unattend-content in config string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1779,9 +1779,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('additional-unattend-content') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.command('additional-unattend-content') + removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.command('remove') .description($('Remove additional-unattend-content in config string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1839,9 +1839,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('additional-unattend-content') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.command('additional-unattend-content') + addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.command('add') .description($('Add additional-unattend-content in config string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "passName":"",\r\n "componentName":"",\r\n "settingName":"",\r\n "content":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1924,9 +1924,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('win-rm') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.command('win-rm') + removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.command('remove') .description($('Remove win-rm in config string or files, e.g. \r\n {\r\n ...\r\n "winRM" : {\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1968,9 +1968,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('win-rm') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.command('win-rm') + addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.command('add') .description($('Add win-rm in config string or files, e.g. \r\n {\r\n ...\r\n "winRM" : {\r\n "listeners":[\r\n {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2020,9 +2020,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('listeners') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.command('listeners') + setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.command('set') .description($('Set listeners in config string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2084,9 +2084,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('listeners') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.command('listeners') + removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.command('remove') .description($('Remove listeners in config string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2134,9 +2134,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('listeners') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.command('listeners') + addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.command('add') .description($('Add listeners in config string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "protocol":"",\r\n "certificateUrl":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2197,9 +2197,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('linux-configuration') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.command('linux-configuration') + setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.command('set') .description($('Set linux-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "linuxConfiguration" : {\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2257,9 +2257,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('linux-configuration') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.command('linux-configuration') + removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.command('remove') .description($('Remove linux-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "linuxConfiguration" : {\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2306,9 +2306,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('linux-configuration') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.command('linux-configuration') + addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.command('add') .description($('Add linux-configuration in config string or files, e.g. \r\n {\r\n ...\r\n "linuxConfiguration" : {\r\n "disablePasswordAuthentication":null,\r\n "ssh":{\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2370,9 +2370,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('ssh') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.command('ssh') + removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.command('remove') .description($('Remove ssh in config string or files, e.g. \r\n {\r\n ...\r\n "ssh" : {\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2414,9 +2414,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('ssh') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.command('ssh') + addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.command('add') .description($('Add ssh in config string or files, e.g. \r\n {\r\n ...\r\n "ssh" : {\r\n "publicKeys":[\r\n {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2466,9 +2466,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('public-keys') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.command('public-keys') + setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.command('set') .description($('Set public-keys in config string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2530,9 +2530,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('public-keys') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.command('public-keys') + removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.command('remove') .description($('Remove public-keys in config string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2580,9 +2580,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('public-keys') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.command('public-keys') + addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.command('add') .description($('Add public-keys in config string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "path":"",\r\n "keyData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2643,9 +2643,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('secrets') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.command('secrets') + removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.command('remove') .description($('Remove secrets in config string or files, e.g. \r\n {\r\n ...\r\n "secrets" : {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2693,9 +2693,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('secrets') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.command('secrets') + addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.command('add') .description($('Add secrets in config string or files, e.g. \r\n {\r\n ...\r\n "secrets" : {\r\n "sourceVault":{\r\n "id":""\r\n },\r\n "vaultCertificates":[\r\n {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2756,9 +2756,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('source-vault') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.command('source-vault') + setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.command('set') .description($('Set source-vault in config string or files, e.g. \r\n {\r\n ...\r\n "sourceVault" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2805,9 +2805,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('source-vault') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.command('source-vault') + removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.command('remove') .description($('Remove source-vault in config string or files, e.g. \r\n {\r\n ...\r\n "sourceVault" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2850,9 +2850,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('source-vault') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.command('source-vault') + addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.command('add') .description($('Add source-vault in config string or files, e.g. \r\n {\r\n ...\r\n "sourceVault" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2902,9 +2902,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('vault-certificates') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.command('vault-certificates') + setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.command('set') .description($('Set vault-certificates in config string or files, e.g. \r\n {\r\n ...\r\n "vaultCertificates" : {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2967,9 +2967,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('vault-certificates') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.command('vault-certificates') + removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.command('remove') .description($('Remove vault-certificates in config string or files, e.g. \r\n {\r\n ...\r\n "vaultCertificates" : {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3018,9 +3018,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('vault-certificates') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.command('vault-certificates') + addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.command('add') .description($('Add vault-certificates in config string or files, e.g. \r\n {\r\n ...\r\n "vaultCertificates" : {\r\n "certificateUrl":"",\r\n "certificateStore":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3081,9 +3081,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('storage-profile') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.command('storage-profile') + removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.command('remove') .description($('Remove storage-profile in config string or files, e.g. \r\n {\r\n ...\r\n "storageProfile" : {\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3130,9 +3130,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('storage-profile') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.command('storage-profile') + addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.command('add') .description($('Add storage-profile in config string or files, e.g. \r\n {\r\n ...\r\n "storageProfile" : {\r\n "imageReference":{\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "osDisk":{\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3193,9 +3193,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('image-reference') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.command('image-reference') + setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.command('set') .description($('Set image-reference in config string or files, e.g. \r\n {\r\n ...\r\n "imageReference" : {\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3274,9 +3274,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('image-reference') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.command('image-reference') + removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.command('remove') .description($('Remove image-reference in config string or files, e.g. \r\n {\r\n ...\r\n "imageReference" : {\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3333,9 +3333,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('image-reference') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.command('image-reference') + addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.command('add') .description($('Add image-reference in config string or files, e.g. \r\n {\r\n ...\r\n "imageReference" : {\r\n "publisher":"",\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3418,9 +3418,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('os-disk') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.command('os-disk') + setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.command('set') .description($('Set os-disk in config string or files, e.g. \r\n {\r\n ...\r\n "osDisk" : {\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3521,9 +3521,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('os-disk') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.command('os-disk') + removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.command('remove') .description($('Remove os-disk in config string or files, e.g. \r\n {\r\n ...\r\n "osDisk" : {\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3590,9 +3590,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('os-disk') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.command('os-disk') + addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.command('add') .description($('Add os-disk in config string or files, e.g. \r\n {\r\n ...\r\n "osDisk" : {\r\n "name":"",\r\n "caching":"",\r\n "createOption":"",\r\n "osType":"",\r\n "image":{\r\n "uri":""\r\n },\r\n "vhdContainers":[\r\n ""\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3697,9 +3697,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImage0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = parametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = parametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('image') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsImage0.command('image') + setparametersCreateOrUpdateVirtualMachineScaleSetsImage0.command('set') .description($('Set image in config string or files, e.g. \r\n {\r\n ...\r\n "image" : {\r\n "uri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3745,9 +3745,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImage1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = parametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = parametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('image') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1.command('image') + removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1.command('remove') .description($('Remove image in config string or files, e.g. \r\n {\r\n ...\r\n "image" : {\r\n "uri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3789,9 +3789,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsImage2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = parametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = parametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('image') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsImage2.command('image') + addparametersCreateOrUpdateVirtualMachineScaleSetsImage2.command('add') .description($('Add image in config string or files, e.g. \r\n {\r\n ...\r\n "image" : {\r\n "uri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3841,9 +3841,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('vhd-containers') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.command('vhd-containers') + setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.command('set') .description($('Set vhd-containers in config string or files, e.g. \r\n {\r\n ...\r\n "vhdContainers" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3883,9 +3883,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('vhd-containers') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.command('vhd-containers') + removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.command('remove') .description($('Remove vhd-containers in config string or files, e.g. \r\n {\r\n ...\r\n "vhdContainers" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3917,9 +3917,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('vhd-containers') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.command('vhd-containers') + addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.command('add') .description($('Add vhd-containers in config string or files, e.g. \r\n {\r\n ...\r\n "vhdContainers" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3958,9 +3958,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('network-profile') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.command('network-profile') + removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.command('remove') .description($('Remove network-profile in config string or files, e.g. \r\n {\r\n ...\r\n "networkProfile" : {\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4002,9 +4002,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('network-profile') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.command('network-profile') + addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.command('add') .description($('Add network-profile in config string or files, e.g. \r\n {\r\n ...\r\n "networkProfile" : {\r\n "networkInterfaceConfigurations":[\r\n {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4054,9 +4054,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('network-interface-configurations') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.command('network-interface-configurations') + setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.command('set') .description($('Set network-interface-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaceConfigurations" : {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4141,9 +4141,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('network-interface-configurations') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.command('network-interface-configurations') + removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.command('remove') .description($('Remove network-interface-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaceConfigurations" : {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4201,9 +4201,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('network-interface-configurations') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.command('network-interface-configurations') + addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.command('add') .description($('Add network-interface-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaceConfigurations" : {\r\n "name":"",\r\n "primary":null,\r\n "ipConfigurations":[\r\n {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4287,9 +4287,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('ip-configurations') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.command('ip-configurations') + setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.command('set') .description($('Set ip-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4385,9 +4385,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('ip-configurations') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.command('ip-configurations') + removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.command('remove') .description($('Remove ip-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4451,9 +4451,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('ip-configurations') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.command('ip-configurations') + addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.command('add') .description($('Add ip-configurations in config string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "name":"",\r\n "subnet":{\r\n "id":""\r\n },\r\n "loadBalancerBackendAddressPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "loadBalancerInboundNatPools":[\r\n {\r\n "id":""\r\n }\r\n ],\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4547,9 +4547,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('subnet') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.command('subnet') + setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.command('set') .description($('Set subnet in config string or files, e.g. \r\n {\r\n ...\r\n "subnet" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4597,9 +4597,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('subnet') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.command('subnet') + removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.command('remove') .description($('Remove subnet in config string or files, e.g. \r\n {\r\n ...\r\n "subnet" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4643,9 +4643,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('subnet') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.command('subnet') + addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.command('add') .description($('Add subnet in config string or files, e.g. \r\n {\r\n ...\r\n "subnet" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4695,9 +4695,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('load-balancer-backend-address-pools') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.command('load-balancer-backend-address-pools') + setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.command('set') .description($('Set load-balancer-backend-address-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerBackendAddressPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4750,9 +4750,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('load-balancer-backend-address-pools') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.command('load-balancer-backend-address-pools') + removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.command('remove') .description($('Remove load-balancer-backend-address-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerBackendAddressPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4797,9 +4797,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('load-balancer-backend-address-pools') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.command('load-balancer-backend-address-pools') + addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.command('add') .description($('Add load-balancer-backend-address-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerBackendAddressPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4849,9 +4849,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('load-balancer-inbound-nat-pools') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.command('load-balancer-inbound-nat-pools') + setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.command('set') .description($('Set load-balancer-inbound-nat-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerInboundNatPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4904,9 +4904,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('load-balancer-inbound-nat-pools') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.command('load-balancer-inbound-nat-pools') + removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.command('remove') .description($('Remove load-balancer-inbound-nat-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerInboundNatPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4951,9 +4951,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('load-balancer-inbound-nat-pools') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.command('load-balancer-inbound-nat-pools') + addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.command('add') .description($('Add load-balancer-inbound-nat-pools in config string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerInboundNatPools" : {\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5003,9 +5003,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('extension-profile') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.command('extension-profile') + removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.command('remove') .description($('Remove extension-profile in config string or files, e.g. \r\n {\r\n ...\r\n "extensionProfile" : {\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5047,9 +5047,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('extension-profile') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.command('extension-profile') + addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.command('add') .description($('Add extension-profile in config string or files, e.g. \r\n {\r\n ...\r\n "extensionProfile" : {\r\n "extensions":[\r\n {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5099,9 +5099,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('set') + var setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('extensions') .description($('Commands to set components of virtual-machine-scale-sets in config file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.command('extensions') + setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.command('set') .description($('Set extensions in config string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5241,9 +5241,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('remove') + var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('extensions') .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.command('extensions') + removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.command('remove') .description($('Remove extensions in config string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5326,9 +5326,9 @@ exports.init = function (cli) { var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = cli.category('vmss'); var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('config') .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('add') + var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('extensions') .description($('Commands to add components of virtual-machine-scale-sets in config file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.command('extensions') + addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.command('add') .description($('Add extensions in config string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "name":"",\r\n "publisher":"",\r\n "virtualMachineScaleSetExtensionType":"",\r\n "typeHandlerVersion":"",\r\n "autoUpgradeMinorVersion":null,\r\n "settings":{\r\n },\r\n "protectedSettings":{\r\n },\r\n "provisioningState":"",\r\n "id":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js index a95998c6fa21..5a648815925b 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js @@ -174,9 +174,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.category('set') + var setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.category('deployment-change-configuration-parameters') .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); - setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.command('deployment-change-configuration-parameters') + setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.command('set') .description($('Set deployment-change-configuration-parameters in change-configuration-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -267,9 +267,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.category('remove') + var removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.category('deployment-change-configuration-parameters') .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); - removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.command('deployment-change-configuration-parameters') + removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.command('remove') .description($('Remove deployment-change-configuration-parameters in change-configuration-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -331,9 +331,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = catparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.category('add') + var addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.category('deployment-change-configuration-parameters') .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); - addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.command('deployment-change-configuration-parameters') + addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.command('add') .description($('Add deployment-change-configuration-parameters in change-configuration-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -428,9 +428,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = catparametersChangeConfigurationByNameDeploymentExtensionConfiguration1.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration1.category('remove') + var removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration1.category('extension-configuration') .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); - removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1.command('extension-configuration') + removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1.command('remove') .description($('Remove extension-configuration in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -477,9 +477,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = catparametersChangeConfigurationByNameDeploymentExtensionConfiguration2.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration2.category('add') + var addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration2.category('extension-configuration') .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); - addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2.command('extension-configuration') + addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2.command('add') .description($('Add extension-configuration in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -540,9 +540,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentAllRoles0 = catparametersChangeConfigurationByNameDeploymentAllRoles0.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationByNameDeploymentAllRoles0 = parametersChangeConfigurationByNameDeploymentAllRoles0.category('set') + var setparametersChangeConfigurationByNameDeploymentAllRoles0 = parametersChangeConfigurationByNameDeploymentAllRoles0.category('all-roles') .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); - setparametersChangeConfigurationByNameDeploymentAllRoles0.command('all-roles') + setparametersChangeConfigurationByNameDeploymentAllRoles0.command('set') .description($('Set all-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -604,9 +604,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentAllRoles1 = catparametersChangeConfigurationByNameDeploymentAllRoles1.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationByNameDeploymentAllRoles1 = parametersChangeConfigurationByNameDeploymentAllRoles1.category('remove') + var removeparametersChangeConfigurationByNameDeploymentAllRoles1 = parametersChangeConfigurationByNameDeploymentAllRoles1.category('all-roles') .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); - removeparametersChangeConfigurationByNameDeploymentAllRoles1.command('all-roles') + removeparametersChangeConfigurationByNameDeploymentAllRoles1.command('remove') .description($('Remove all-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -654,9 +654,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentAllRoles2 = catparametersChangeConfigurationByNameDeploymentAllRoles2.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationByNameDeploymentAllRoles2 = parametersChangeConfigurationByNameDeploymentAllRoles2.category('add') + var addparametersChangeConfigurationByNameDeploymentAllRoles2 = parametersChangeConfigurationByNameDeploymentAllRoles2.category('all-roles') .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); - addparametersChangeConfigurationByNameDeploymentAllRoles2.command('all-roles') + addparametersChangeConfigurationByNameDeploymentAllRoles2.command('add') .description($('Add all-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -717,9 +717,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentNamedRoles0 = catparametersChangeConfigurationByNameDeploymentNamedRoles0.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationByNameDeploymentNamedRoles0 = parametersChangeConfigurationByNameDeploymentNamedRoles0.category('set') + var setparametersChangeConfigurationByNameDeploymentNamedRoles0 = parametersChangeConfigurationByNameDeploymentNamedRoles0.category('named-roles') .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); - setparametersChangeConfigurationByNameDeploymentNamedRoles0.command('named-roles') + setparametersChangeConfigurationByNameDeploymentNamedRoles0.command('set') .description($('Set named-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -781,9 +781,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentNamedRoles1 = catparametersChangeConfigurationByNameDeploymentNamedRoles1.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationByNameDeploymentNamedRoles1 = parametersChangeConfigurationByNameDeploymentNamedRoles1.category('remove') + var removeparametersChangeConfigurationByNameDeploymentNamedRoles1 = parametersChangeConfigurationByNameDeploymentNamedRoles1.category('named-roles') .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); - removeparametersChangeConfigurationByNameDeploymentNamedRoles1.command('named-roles') + removeparametersChangeConfigurationByNameDeploymentNamedRoles1.command('remove') .description($('Remove named-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -831,9 +831,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentNamedRoles2 = catparametersChangeConfigurationByNameDeploymentNamedRoles2.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationByNameDeploymentNamedRoles2 = parametersChangeConfigurationByNameDeploymentNamedRoles2.category('add') + var addparametersChangeConfigurationByNameDeploymentNamedRoles2 = parametersChangeConfigurationByNameDeploymentNamedRoles2.category('named-roles') .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); - addparametersChangeConfigurationByNameDeploymentNamedRoles2.command('named-roles') + addparametersChangeConfigurationByNameDeploymentNamedRoles2.command('add') .description($('Add named-roles in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -894,9 +894,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentExtensions0 = catparametersChangeConfigurationByNameDeploymentExtensions0.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationByNameDeploymentExtensions0 = parametersChangeConfigurationByNameDeploymentExtensions0.category('set') + var setparametersChangeConfigurationByNameDeploymentExtensions0 = parametersChangeConfigurationByNameDeploymentExtensions0.category('extensions') .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); - setparametersChangeConfigurationByNameDeploymentExtensions0.command('extensions') + setparametersChangeConfigurationByNameDeploymentExtensions0.command('set') .description($('Set extensions in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -937,9 +937,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentExtensions1 = catparametersChangeConfigurationByNameDeploymentExtensions1.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationByNameDeploymentExtensions1 = parametersChangeConfigurationByNameDeploymentExtensions1.category('remove') + var removeparametersChangeConfigurationByNameDeploymentExtensions1 = parametersChangeConfigurationByNameDeploymentExtensions1.category('extensions') .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); - removeparametersChangeConfigurationByNameDeploymentExtensions1.command('extensions') + removeparametersChangeConfigurationByNameDeploymentExtensions1.command('remove') .description($('Remove extensions in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -972,9 +972,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationByNameDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationByNameDeploymentExtensions2 = catparametersChangeConfigurationByNameDeploymentExtensions2.category('change-configuration-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationByNameDeploymentExtensions2 = parametersChangeConfigurationByNameDeploymentExtensions2.category('add') + var addparametersChangeConfigurationByNameDeploymentExtensions2 = parametersChangeConfigurationByNameDeploymentExtensions2.category('extensions') .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); - addparametersChangeConfigurationByNameDeploymentExtensions2.command('extensions') + addparametersChangeConfigurationByNameDeploymentExtensions2.command('add') .description($('Add extensions in change-configuration-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1149,9 +1149,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.category('set') + var setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.category('deployment-change-configuration-parameters') .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); - setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.command('deployment-change-configuration-parameters') + setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.command('set') .description($('Set deployment-change-configuration-parameters in change-configuration-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1242,9 +1242,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.category('remove') + var removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.category('deployment-change-configuration-parameters') .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); - removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.command('deployment-change-configuration-parameters') + removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.command('remove') .description($('Remove deployment-change-configuration-parameters in change-configuration-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1306,9 +1306,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = catparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.category('add') + var addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.category('deployment-change-configuration-parameters') .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); - addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.command('deployment-change-configuration-parameters') + addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.command('add') .description($('Add deployment-change-configuration-parameters in change-configuration-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "mode":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1403,9 +1403,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.category('remove') + var removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.category('extension-configuration') .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); - removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.command('extension-configuration') + removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.command('remove') .description($('Remove extension-configuration in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1452,9 +1452,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.category('add') + var addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.category('extension-configuration') .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); - addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.command('extension-configuration') + addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.command('add') .description($('Add extension-configuration in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1515,9 +1515,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentAllRoles0 = catparametersChangeConfigurationBySlotDeploymentAllRoles0.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationBySlotDeploymentAllRoles0 = parametersChangeConfigurationBySlotDeploymentAllRoles0.category('set') + var setparametersChangeConfigurationBySlotDeploymentAllRoles0 = parametersChangeConfigurationBySlotDeploymentAllRoles0.category('all-roles') .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); - setparametersChangeConfigurationBySlotDeploymentAllRoles0.command('all-roles') + setparametersChangeConfigurationBySlotDeploymentAllRoles0.command('set') .description($('Set all-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1579,9 +1579,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentAllRoles1 = catparametersChangeConfigurationBySlotDeploymentAllRoles1.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationBySlotDeploymentAllRoles1 = parametersChangeConfigurationBySlotDeploymentAllRoles1.category('remove') + var removeparametersChangeConfigurationBySlotDeploymentAllRoles1 = parametersChangeConfigurationBySlotDeploymentAllRoles1.category('all-roles') .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); - removeparametersChangeConfigurationBySlotDeploymentAllRoles1.command('all-roles') + removeparametersChangeConfigurationBySlotDeploymentAllRoles1.command('remove') .description($('Remove all-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1629,9 +1629,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentAllRoles2 = catparametersChangeConfigurationBySlotDeploymentAllRoles2.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationBySlotDeploymentAllRoles2 = parametersChangeConfigurationBySlotDeploymentAllRoles2.category('add') + var addparametersChangeConfigurationBySlotDeploymentAllRoles2 = parametersChangeConfigurationBySlotDeploymentAllRoles2.category('all-roles') .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); - addparametersChangeConfigurationBySlotDeploymentAllRoles2.command('all-roles') + addparametersChangeConfigurationBySlotDeploymentAllRoles2.command('add') .description($('Add all-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1692,9 +1692,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentNamedRoles0 = catparametersChangeConfigurationBySlotDeploymentNamedRoles0.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationBySlotDeploymentNamedRoles0 = parametersChangeConfigurationBySlotDeploymentNamedRoles0.category('set') + var setparametersChangeConfigurationBySlotDeploymentNamedRoles0 = parametersChangeConfigurationBySlotDeploymentNamedRoles0.category('named-roles') .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); - setparametersChangeConfigurationBySlotDeploymentNamedRoles0.command('named-roles') + setparametersChangeConfigurationBySlotDeploymentNamedRoles0.command('set') .description($('Set named-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1756,9 +1756,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentNamedRoles1 = catparametersChangeConfigurationBySlotDeploymentNamedRoles1.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationBySlotDeploymentNamedRoles1 = parametersChangeConfigurationBySlotDeploymentNamedRoles1.category('remove') + var removeparametersChangeConfigurationBySlotDeploymentNamedRoles1 = parametersChangeConfigurationBySlotDeploymentNamedRoles1.category('named-roles') .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); - removeparametersChangeConfigurationBySlotDeploymentNamedRoles1.command('named-roles') + removeparametersChangeConfigurationBySlotDeploymentNamedRoles1.command('remove') .description($('Remove named-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1806,9 +1806,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentNamedRoles2 = catparametersChangeConfigurationBySlotDeploymentNamedRoles2.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationBySlotDeploymentNamedRoles2 = parametersChangeConfigurationBySlotDeploymentNamedRoles2.category('add') + var addparametersChangeConfigurationBySlotDeploymentNamedRoles2 = parametersChangeConfigurationBySlotDeploymentNamedRoles2.category('named-roles') .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); - addparametersChangeConfigurationBySlotDeploymentNamedRoles2.command('named-roles') + addparametersChangeConfigurationBySlotDeploymentNamedRoles2.command('add') .description($('Add named-roles in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1869,9 +1869,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentExtensions0 = catparametersChangeConfigurationBySlotDeploymentExtensions0.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersChangeConfigurationBySlotDeploymentExtensions0 = parametersChangeConfigurationBySlotDeploymentExtensions0.category('set') + var setparametersChangeConfigurationBySlotDeploymentExtensions0 = parametersChangeConfigurationBySlotDeploymentExtensions0.category('extensions') .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); - setparametersChangeConfigurationBySlotDeploymentExtensions0.command('extensions') + setparametersChangeConfigurationBySlotDeploymentExtensions0.command('set') .description($('Set extensions in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1912,9 +1912,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentExtensions1 = catparametersChangeConfigurationBySlotDeploymentExtensions1.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersChangeConfigurationBySlotDeploymentExtensions1 = parametersChangeConfigurationBySlotDeploymentExtensions1.category('remove') + var removeparametersChangeConfigurationBySlotDeploymentExtensions1 = parametersChangeConfigurationBySlotDeploymentExtensions1.category('extensions') .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); - removeparametersChangeConfigurationBySlotDeploymentExtensions1.command('extensions') + removeparametersChangeConfigurationBySlotDeploymentExtensions1.command('remove') .description($('Remove extensions in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -1947,9 +1947,9 @@ exports.init = function (cli) { var catparametersChangeConfigurationBySlotDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersChangeConfigurationBySlotDeploymentExtensions2 = catparametersChangeConfigurationBySlotDeploymentExtensions2.category('change-configuration-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersChangeConfigurationBySlotDeploymentExtensions2 = parametersChangeConfigurationBySlotDeploymentExtensions2.category('add') + var addparametersChangeConfigurationBySlotDeploymentExtensions2 = parametersChangeConfigurationBySlotDeploymentExtensions2.category('extensions') .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); - addparametersChangeConfigurationBySlotDeploymentExtensions2.command('extensions') + addparametersChangeConfigurationBySlotDeploymentExtensions2.command('add') .description($('Add extensions in change-configuration-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2127,9 +2127,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentDeploymentCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters0 = catparametersCreateDeploymentDeploymentCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersCreateDeploymentDeploymentCreateParameters0 = parametersCreateDeploymentDeploymentCreateParameters0.category('set') + var setparametersCreateDeploymentDeploymentCreateParameters0 = parametersCreateDeploymentDeploymentCreateParameters0.category('deployment-create-parameters') .description($('Commands to set components of deployment in create-parameters file.')); - setparametersCreateDeploymentDeploymentCreateParameters0.command('deployment-create-parameters') + setparametersCreateDeploymentDeploymentCreateParameters0.command('set') .description($('Set deployment-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "name":"",\r\n "packageUri":"",\r\n "startDeployment":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2254,9 +2254,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentDeploymentCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters1 = catparametersCreateDeploymentDeploymentCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersCreateDeploymentDeploymentCreateParameters1 = parametersCreateDeploymentDeploymentCreateParameters1.category('remove') + var removeparametersCreateDeploymentDeploymentCreateParameters1 = parametersCreateDeploymentDeploymentCreateParameters1.category('deployment-create-parameters') .description($('Commands to remove components of deployment in create-parameters file.')); - removeparametersCreateDeploymentDeploymentCreateParameters1.command('deployment-create-parameters') + removeparametersCreateDeploymentDeploymentCreateParameters1.command('remove') .description($('Remove deployment-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "name":"",\r\n "packageUri":"",\r\n "startDeployment":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2333,9 +2333,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentDeploymentCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters2 = catparametersCreateDeploymentDeploymentCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersCreateDeploymentDeploymentCreateParameters2 = parametersCreateDeploymentDeploymentCreateParameters2.category('add') + var addparametersCreateDeploymentDeploymentCreateParameters2 = parametersCreateDeploymentDeploymentCreateParameters2.category('deployment-create-parameters') .description($('Commands to add components of deployment in create-parameters file.')); - addparametersCreateDeploymentDeploymentCreateParameters2.command('deployment-create-parameters') + addparametersCreateDeploymentDeploymentCreateParameters2.command('add') .description($('Add deployment-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "name":"",\r\n "packageUri":"",\r\n "startDeployment":null,\r\n "treatWarningsAsError":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2464,9 +2464,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensionConfiguration1 = catparametersCreateDeploymentExtensionConfiguration1.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersCreateDeploymentExtensionConfiguration1 = parametersCreateDeploymentExtensionConfiguration1.category('remove') + var removeparametersCreateDeploymentExtensionConfiguration1 = parametersCreateDeploymentExtensionConfiguration1.category('extension-configuration') .description($('Commands to remove components of deployment in create-parameters file.')); - removeparametersCreateDeploymentExtensionConfiguration1.command('extension-configuration') + removeparametersCreateDeploymentExtensionConfiguration1.command('remove') .description($('Remove extension-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2513,9 +2513,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensionConfiguration2 = catparametersCreateDeploymentExtensionConfiguration2.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersCreateDeploymentExtensionConfiguration2 = parametersCreateDeploymentExtensionConfiguration2.category('add') + var addparametersCreateDeploymentExtensionConfiguration2 = parametersCreateDeploymentExtensionConfiguration2.category('extension-configuration') .description($('Commands to add components of deployment in create-parameters file.')); - addparametersCreateDeploymentExtensionConfiguration2.command('extension-configuration') + addparametersCreateDeploymentExtensionConfiguration2.command('add') .description($('Add extension-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2576,9 +2576,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles0 = catparametersCreateDeploymentAllRoles0.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersCreateDeploymentAllRoles0 = parametersCreateDeploymentAllRoles0.category('set') + var setparametersCreateDeploymentAllRoles0 = parametersCreateDeploymentAllRoles0.category('all-roles') .description($('Commands to set components of deployment in create-parameters file.')); - setparametersCreateDeploymentAllRoles0.command('all-roles') + setparametersCreateDeploymentAllRoles0.command('set') .description($('Set all-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2640,9 +2640,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles1 = catparametersCreateDeploymentAllRoles1.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersCreateDeploymentAllRoles1 = parametersCreateDeploymentAllRoles1.category('remove') + var removeparametersCreateDeploymentAllRoles1 = parametersCreateDeploymentAllRoles1.category('all-roles') .description($('Commands to remove components of deployment in create-parameters file.')); - removeparametersCreateDeploymentAllRoles1.command('all-roles') + removeparametersCreateDeploymentAllRoles1.command('remove') .description($('Remove all-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2690,9 +2690,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles2 = catparametersCreateDeploymentAllRoles2.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersCreateDeploymentAllRoles2 = parametersCreateDeploymentAllRoles2.category('add') + var addparametersCreateDeploymentAllRoles2 = parametersCreateDeploymentAllRoles2.category('all-roles') .description($('Commands to add components of deployment in create-parameters file.')); - addparametersCreateDeploymentAllRoles2.command('all-roles') + addparametersCreateDeploymentAllRoles2.command('add') .description($('Add all-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2753,9 +2753,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles0 = catparametersCreateDeploymentNamedRoles0.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersCreateDeploymentNamedRoles0 = parametersCreateDeploymentNamedRoles0.category('set') + var setparametersCreateDeploymentNamedRoles0 = parametersCreateDeploymentNamedRoles0.category('named-roles') .description($('Commands to set components of deployment in create-parameters file.')); - setparametersCreateDeploymentNamedRoles0.command('named-roles') + setparametersCreateDeploymentNamedRoles0.command('set') .description($('Set named-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2817,9 +2817,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles1 = catparametersCreateDeploymentNamedRoles1.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersCreateDeploymentNamedRoles1 = parametersCreateDeploymentNamedRoles1.category('remove') + var removeparametersCreateDeploymentNamedRoles1 = parametersCreateDeploymentNamedRoles1.category('named-roles') .description($('Commands to remove components of deployment in create-parameters file.')); - removeparametersCreateDeploymentNamedRoles1.command('named-roles') + removeparametersCreateDeploymentNamedRoles1.command('remove') .description($('Remove named-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2867,9 +2867,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles2 = catparametersCreateDeploymentNamedRoles2.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersCreateDeploymentNamedRoles2 = parametersCreateDeploymentNamedRoles2.category('add') + var addparametersCreateDeploymentNamedRoles2 = parametersCreateDeploymentNamedRoles2.category('named-roles') .description($('Commands to add components of deployment in create-parameters file.')); - addparametersCreateDeploymentNamedRoles2.command('named-roles') + addparametersCreateDeploymentNamedRoles2.command('add') .description($('Add named-roles in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2930,9 +2930,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions0 = catparametersCreateDeploymentExtensions0.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersCreateDeploymentExtensions0 = parametersCreateDeploymentExtensions0.category('set') + var setparametersCreateDeploymentExtensions0 = parametersCreateDeploymentExtensions0.category('extensions') .description($('Commands to set components of deployment in create-parameters file.')); - setparametersCreateDeploymentExtensions0.command('extensions') + setparametersCreateDeploymentExtensions0.command('set') .description($('Set extensions in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -2973,9 +2973,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions1 = catparametersCreateDeploymentExtensions1.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersCreateDeploymentExtensions1 = parametersCreateDeploymentExtensions1.category('remove') + var removeparametersCreateDeploymentExtensions1 = parametersCreateDeploymentExtensions1.category('extensions') .description($('Commands to remove components of deployment in create-parameters file.')); - removeparametersCreateDeploymentExtensions1.command('extensions') + removeparametersCreateDeploymentExtensions1.command('remove') .description($('Remove extensions in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3008,9 +3008,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions2 = catparametersCreateDeploymentExtensions2.category('create-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersCreateDeploymentExtensions2 = parametersCreateDeploymentExtensions2.category('add') + var addparametersCreateDeploymentExtensions2 = parametersCreateDeploymentExtensions2.category('extensions') .description($('Commands to add components of deployment in create-parameters file.')); - addparametersCreateDeploymentExtensions2.command('extensions') + addparametersCreateDeploymentExtensions2.command('add') .description($('Add extensions in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3291,9 +3291,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.category('set') + var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.category('deployment-delete-role-instance-parameters') .description($('Commands to set components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.command('deployment-delete-role-instance-parameters') + setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.command('set') .description($('Set deployment-delete-role-instance-parameters in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "name":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3339,9 +3339,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.category('remove') + var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.category('deployment-delete-role-instance-parameters') .description($('Commands to remove components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.command('deployment-delete-role-instance-parameters') + removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.command('remove') .description($('Remove deployment-delete-role-instance-parameters in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "name":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3383,9 +3383,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.category('add') + var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.category('deployment-delete-role-instance-parameters') .description($('Commands to add components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.command('deployment-delete-role-instance-parameters') + addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.command('add') .description($('Add deployment-delete-role-instance-parameters in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "name":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3435,9 +3435,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.category('set') + var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.category('name') .description($('Commands to set components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.command('name') + setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.command('set') .description($('Set name in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "name" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3477,9 +3477,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.category('remove') + var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.category('name') .description($('Commands to remove components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.command('name') + removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.command('remove') .description($('Remove name in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "name" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3511,9 +3511,9 @@ exports.init = function (cli) { var catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = catparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.category('delete-role-instance-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.category('add') + var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.category('name') .description($('Commands to add components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.command('name') + addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.command('add') .description($('Add name in delete-role-instance-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "name" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3732,9 +3732,9 @@ exports.init = function (cli) { var catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.category('get-package-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.category('set') + var setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.category('deployment-get-package-parameters') .description($('Commands to set components of deployment in get-package-by-name-parameters file.')); - setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.command('deployment-get-package-parameters') + setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.command('set') .description($('Set deployment-get-package-parameters in get-package-by-name-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3792,9 +3792,9 @@ exports.init = function (cli) { var catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.category('get-package-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.category('remove') + var removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.category('deployment-get-package-parameters') .description($('Commands to remove components of deployment in get-package-by-name-parameters file.')); - removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.command('deployment-get-package-parameters') + removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.command('remove') .description($('Remove deployment-get-package-parameters in get-package-by-name-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -3841,9 +3841,9 @@ exports.init = function (cli) { var catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = catparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.category('get-package-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.category('add') + var addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.category('deployment-get-package-parameters') .description($('Commands to add components of deployment in get-package-by-name-parameters file.')); - addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.command('deployment-get-package-parameters') + addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.command('add') .description($('Add deployment-get-package-parameters in get-package-by-name-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4019,9 +4019,9 @@ exports.init = function (cli) { var catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.category('get-package-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.category('set') + var setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.category('deployment-get-package-parameters') .description($('Commands to set components of deployment in get-package-by-slot-parameters file.')); - setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.command('deployment-get-package-parameters') + setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.command('set') .description($('Set deployment-get-package-parameters in get-package-by-slot-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4079,9 +4079,9 @@ exports.init = function (cli) { var catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.category('get-package-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.category('remove') + var removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.category('deployment-get-package-parameters') .description($('Commands to remove components of deployment in get-package-by-slot-parameters file.')); - removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.command('deployment-get-package-parameters') + removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.command('remove') .description($('Remove deployment-get-package-parameters in get-package-by-slot-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4128,9 +4128,9 @@ exports.init = function (cli) { var catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = catparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.category('get-package-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.category('add') + var addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.category('deployment-get-package-parameters') .description($('Commands to add components of deployment in get-package-by-slot-parameters file.')); - addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.command('deployment-get-package-parameters') + addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.command('add') .description($('Add deployment-get-package-parameters in get-package-by-slot-parameters string or files, e.g. \r\n{\r\n "containerUri":"",\r\n "overwriteExisting":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4652,9 +4652,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('rollback-update-or-upgrade-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('set') + var setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to set components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.command('deployment-rollback-update-or-upgrade-parameters') + setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.command('set') .description($('Set deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4711,9 +4711,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('rollback-update-or-upgrade-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('remove') + var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.command('deployment-rollback-update-or-upgrade-parameters') + removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.command('remove') .description($('Remove deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4760,9 +4760,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('rollback-update-or-upgrade-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('add') + var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.command('deployment-rollback-update-or-upgrade-parameters') + addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.command('add') .description($('Add deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4823,9 +4823,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.category('rollback-update-or-upgrade-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.category('remove') + var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.category('mode') .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.command('mode') + removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.command('remove') .description($('Remove mode in rollback-update-or-upgrade-by-deployment-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -4855,9 +4855,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = catparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.category('rollback-update-or-upgrade-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.category('add') + var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.category('mode') .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.command('mode') + addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.command('add') .description($('Add mode in rollback-update-or-upgrade-by-deployment-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5010,9 +5010,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('rollback-update-or-upgrade-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('set') + var setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to set components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.command('deployment-rollback-update-or-upgrade-parameters') + setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.command('set') .description($('Set deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5069,9 +5069,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('rollback-update-or-upgrade-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('remove') + var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.command('deployment-rollback-update-or-upgrade-parameters') + removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.command('remove') .description($('Remove deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5118,9 +5118,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('rollback-update-or-upgrade-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('add') + var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.command('deployment-rollback-update-or-upgrade-parameters') + addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.command('add') .description($('Add deployment-rollback-update-or-upgrade-parameters in rollback-update-or-upgrade-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "force":false,\r\n "mode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5181,9 +5181,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.category('rollback-update-or-upgrade-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.category('remove') + var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.category('mode') .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.command('mode') + removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.command('remove') .description($('Remove mode in rollback-update-or-upgrade-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5213,9 +5213,9 @@ exports.init = function (cli) { var catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = catparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.category('rollback-update-or-upgrade-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.category('add') + var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.category('mode') .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.command('mode') + addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.command('add') .description($('Add mode in rollback-update-or-upgrade-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5414,9 +5414,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('update-status-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('remove') + var removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') .description($('Commands to remove components of deployment in update-status-by-deployment-name-parameters file.')); - removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.command('deployment-update-status-parameters') + removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.command('remove') .description($('Remove deployment-update-status-parameters in update-status-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "status":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5458,9 +5458,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('update-status-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('add') + var addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') .description($('Commands to add components of deployment in update-status-by-deployment-name-parameters file.')); - addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.command('deployment-update-status-parameters') + addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.command('add') .description($('Add deployment-update-status-parameters in update-status-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "status":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5510,9 +5510,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentNameDeploymentStatus1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentNameDeploymentStatus1 = catparametersUpdateStatusByDeploymentNameDeploymentStatus1.category('update-status-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpdateStatusByDeploymentNameDeploymentStatus1 = parametersUpdateStatusByDeploymentNameDeploymentStatus1.category('remove') + var removeparametersUpdateStatusByDeploymentNameDeploymentStatus1 = parametersUpdateStatusByDeploymentNameDeploymentStatus1.category('status') .description($('Commands to remove components of deployment in update-status-by-deployment-name-parameters file.')); - removeparametersUpdateStatusByDeploymentNameDeploymentStatus1.command('status') + removeparametersUpdateStatusByDeploymentNameDeploymentStatus1.command('remove') .description($('Remove status in update-status-by-deployment-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "status" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5542,9 +5542,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentNameDeploymentStatus2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentNameDeploymentStatus2 = catparametersUpdateStatusByDeploymentNameDeploymentStatus2.category('update-status-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpdateStatusByDeploymentNameDeploymentStatus2 = parametersUpdateStatusByDeploymentNameDeploymentStatus2.category('add') + var addparametersUpdateStatusByDeploymentNameDeploymentStatus2 = parametersUpdateStatusByDeploymentNameDeploymentStatus2.category('status') .description($('Commands to add components of deployment in update-status-by-deployment-name-parameters file.')); - addparametersUpdateStatusByDeploymentNameDeploymentStatus2.command('status') + addparametersUpdateStatusByDeploymentNameDeploymentStatus2.command('add') .description($('Add status in update-status-by-deployment-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "status" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5696,9 +5696,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('update-status-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('remove') + var removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') .description($('Commands to remove components of deployment in update-status-by-deployment-slot-parameters file.')); - removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.command('deployment-update-status-parameters') + removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.command('remove') .description($('Remove deployment-update-status-parameters in update-status-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "status":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5740,9 +5740,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('update-status-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('add') + var addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') .description($('Commands to add components of deployment in update-status-by-deployment-slot-parameters file.')); - addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.command('deployment-update-status-parameters') + addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.command('add') .description($('Add deployment-update-status-parameters in update-status-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "status":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5792,9 +5792,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentSlotDeploymentStatus1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentSlotDeploymentStatus1 = catparametersUpdateStatusByDeploymentSlotDeploymentStatus1.category('update-status-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1 = parametersUpdateStatusByDeploymentSlotDeploymentStatus1.category('remove') + var removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1 = parametersUpdateStatusByDeploymentSlotDeploymentStatus1.category('status') .description($('Commands to remove components of deployment in update-status-by-deployment-slot-parameters file.')); - removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1.command('status') + removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1.command('remove') .description($('Remove status in update-status-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "status" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -5824,9 +5824,9 @@ exports.init = function (cli) { var catparametersUpdateStatusByDeploymentSlotDeploymentStatus2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpdateStatusByDeploymentSlotDeploymentStatus2 = catparametersUpdateStatusByDeploymentSlotDeploymentStatus2.category('update-status-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpdateStatusByDeploymentSlotDeploymentStatus2 = parametersUpdateStatusByDeploymentSlotDeploymentStatus2.category('add') + var addparametersUpdateStatusByDeploymentSlotDeploymentStatus2 = parametersUpdateStatusByDeploymentSlotDeploymentStatus2.category('status') .description($('Commands to add components of deployment in update-status-by-deployment-slot-parameters file.')); - addparametersUpdateStatusByDeploymentSlotDeploymentStatus2.command('status') + addparametersUpdateStatusByDeploymentSlotDeploymentStatus2.command('add') .description($('Add status in update-status-by-deployment-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "status" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6004,9 +6004,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('set') + var setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('deployment-upgrade-parameters') .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.command('deployment-upgrade-parameters') + setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.command('set') .description($('Set deployment-upgrade-parameters in upgrade-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6129,9 +6129,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('remove') + var removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('deployment-upgrade-parameters') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.command('deployment-upgrade-parameters') + removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.command('remove') .description($('Remove deployment-upgrade-parameters in upgrade-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6208,9 +6208,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = catparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('add') + var addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('deployment-upgrade-parameters') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.command('deployment-upgrade-parameters') + addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.command('add') .description($('Add deployment-upgrade-parameters in upgrade-by-name-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6337,9 +6337,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentExtensionConfiguration1 = catparametersUpgradeByNameDeploymentExtensionConfiguration1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentExtensionConfiguration1 = parametersUpgradeByNameDeploymentExtensionConfiguration1.category('remove') + var removeparametersUpgradeByNameDeploymentExtensionConfiguration1 = parametersUpgradeByNameDeploymentExtensionConfiguration1.category('extension-configuration') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentExtensionConfiguration1.command('extension-configuration') + removeparametersUpgradeByNameDeploymentExtensionConfiguration1.command('remove') .description($('Remove extension-configuration in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6386,9 +6386,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentExtensionConfiguration2 = catparametersUpgradeByNameDeploymentExtensionConfiguration2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentExtensionConfiguration2 = parametersUpgradeByNameDeploymentExtensionConfiguration2.category('add') + var addparametersUpgradeByNameDeploymentExtensionConfiguration2 = parametersUpgradeByNameDeploymentExtensionConfiguration2.category('extension-configuration') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentExtensionConfiguration2.command('extension-configuration') + addparametersUpgradeByNameDeploymentExtensionConfiguration2.command('add') .description($('Add extension-configuration in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6449,9 +6449,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentAllRoles0 = catparametersUpgradeByNameDeploymentAllRoles0.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeByNameDeploymentAllRoles0 = parametersUpgradeByNameDeploymentAllRoles0.category('set') + var setparametersUpgradeByNameDeploymentAllRoles0 = parametersUpgradeByNameDeploymentAllRoles0.category('all-roles') .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentAllRoles0.command('all-roles') + setparametersUpgradeByNameDeploymentAllRoles0.command('set') .description($('Set all-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6513,9 +6513,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentAllRoles1 = catparametersUpgradeByNameDeploymentAllRoles1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentAllRoles1 = parametersUpgradeByNameDeploymentAllRoles1.category('remove') + var removeparametersUpgradeByNameDeploymentAllRoles1 = parametersUpgradeByNameDeploymentAllRoles1.category('all-roles') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentAllRoles1.command('all-roles') + removeparametersUpgradeByNameDeploymentAllRoles1.command('remove') .description($('Remove all-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6563,9 +6563,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentAllRoles2 = catparametersUpgradeByNameDeploymentAllRoles2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentAllRoles2 = parametersUpgradeByNameDeploymentAllRoles2.category('add') + var addparametersUpgradeByNameDeploymentAllRoles2 = parametersUpgradeByNameDeploymentAllRoles2.category('all-roles') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentAllRoles2.command('all-roles') + addparametersUpgradeByNameDeploymentAllRoles2.command('add') .description($('Add all-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6626,9 +6626,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentNamedRoles0 = catparametersUpgradeByNameDeploymentNamedRoles0.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeByNameDeploymentNamedRoles0 = parametersUpgradeByNameDeploymentNamedRoles0.category('set') + var setparametersUpgradeByNameDeploymentNamedRoles0 = parametersUpgradeByNameDeploymentNamedRoles0.category('named-roles') .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentNamedRoles0.command('named-roles') + setparametersUpgradeByNameDeploymentNamedRoles0.command('set') .description($('Set named-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6690,9 +6690,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentNamedRoles1 = catparametersUpgradeByNameDeploymentNamedRoles1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentNamedRoles1 = parametersUpgradeByNameDeploymentNamedRoles1.category('remove') + var removeparametersUpgradeByNameDeploymentNamedRoles1 = parametersUpgradeByNameDeploymentNamedRoles1.category('named-roles') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentNamedRoles1.command('named-roles') + removeparametersUpgradeByNameDeploymentNamedRoles1.command('remove') .description($('Remove named-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6740,9 +6740,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentNamedRoles2 = catparametersUpgradeByNameDeploymentNamedRoles2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentNamedRoles2 = parametersUpgradeByNameDeploymentNamedRoles2.category('add') + var addparametersUpgradeByNameDeploymentNamedRoles2 = parametersUpgradeByNameDeploymentNamedRoles2.category('named-roles') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentNamedRoles2.command('named-roles') + addparametersUpgradeByNameDeploymentNamedRoles2.command('add') .description($('Add named-roles in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6803,9 +6803,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentExtensions0 = catparametersUpgradeByNameDeploymentExtensions0.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeByNameDeploymentExtensions0 = parametersUpgradeByNameDeploymentExtensions0.category('set') + var setparametersUpgradeByNameDeploymentExtensions0 = parametersUpgradeByNameDeploymentExtensions0.category('extensions') .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentExtensions0.command('extensions') + setparametersUpgradeByNameDeploymentExtensions0.command('set') .description($('Set extensions in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6846,9 +6846,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentExtensions1 = catparametersUpgradeByNameDeploymentExtensions1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentExtensions1 = parametersUpgradeByNameDeploymentExtensions1.category('remove') + var removeparametersUpgradeByNameDeploymentExtensions1 = parametersUpgradeByNameDeploymentExtensions1.category('extensions') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentExtensions1.command('extensions') + removeparametersUpgradeByNameDeploymentExtensions1.command('remove') .description($('Remove extensions in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6881,9 +6881,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentExtensions2 = catparametersUpgradeByNameDeploymentExtensions2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentExtensions2 = parametersUpgradeByNameDeploymentExtensions2.category('add') + var addparametersUpgradeByNameDeploymentExtensions2 = parametersUpgradeByNameDeploymentExtensions2.category('extensions') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentExtensions2.command('extensions') + addparametersUpgradeByNameDeploymentExtensions2.command('add') .description($('Add extensions in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6922,9 +6922,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentMode1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentMode1 = catparametersUpgradeByNameDeploymentMode1.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeByNameDeploymentMode1 = parametersUpgradeByNameDeploymentMode1.category('remove') + var removeparametersUpgradeByNameDeploymentMode1 = parametersUpgradeByNameDeploymentMode1.category('mode') .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); - removeparametersUpgradeByNameDeploymentMode1.command('mode') + removeparametersUpgradeByNameDeploymentMode1.command('remove') .description($('Remove mode in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -6954,9 +6954,9 @@ exports.init = function (cli) { var catparametersUpgradeByNameDeploymentMode2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeByNameDeploymentMode2 = catparametersUpgradeByNameDeploymentMode2.category('upgrade-by-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeByNameDeploymentMode2 = parametersUpgradeByNameDeploymentMode2.category('add') + var addparametersUpgradeByNameDeploymentMode2 = parametersUpgradeByNameDeploymentMode2.category('mode') .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); - addparametersUpgradeByNameDeploymentMode2.command('mode') + addparametersUpgradeByNameDeploymentMode2.command('add') .description($('Add mode in upgrade-by-name-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7134,9 +7134,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0 = catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.category('set') + var setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.category('deployment-upgrade-parameters') .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); - setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.command('deployment-upgrade-parameters') + setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.command('set') .description($('Set deployment-upgrade-parameters in upgrade-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7259,9 +7259,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1 = catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.category('remove') + var removeparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.category('deployment-upgrade-parameters') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.command('deployment-upgrade-parameters') + removeparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.command('remove') .description($('Remove deployment-upgrade-parameters in upgrade-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7338,9 +7338,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2 = catparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.category('add') + var addparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.category('deployment-upgrade-parameters') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.command('deployment-upgrade-parameters') + addparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.command('add') .description($('Add deployment-upgrade-parameters in upgrade-by-slot-parameters string or files, e.g. \r\n{\r\n "configuration":"",\r\n "extendedProperties":{\r\n },\r\n "extensionConfiguration":{\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n },\r\n "force":false,\r\n "label":"",\r\n "mode":0,\r\n "packageUri":"",\r\n "roleToUpgrade":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7467,9 +7467,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentExtensionConfiguration1 = catparametersUpgradeBySlotDeploymentExtensionConfiguration1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentExtensionConfiguration1 = parametersUpgradeBySlotDeploymentExtensionConfiguration1.category('remove') + var removeparametersUpgradeBySlotDeploymentExtensionConfiguration1 = parametersUpgradeBySlotDeploymentExtensionConfiguration1.category('extension-configuration') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentExtensionConfiguration1.command('extension-configuration') + removeparametersUpgradeBySlotDeploymentExtensionConfiguration1.command('remove') .description($('Remove extension-configuration in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7516,9 +7516,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentExtensionConfiguration2 = catparametersUpgradeBySlotDeploymentExtensionConfiguration2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentExtensionConfiguration2 = parametersUpgradeBySlotDeploymentExtensionConfiguration2.category('add') + var addparametersUpgradeBySlotDeploymentExtensionConfiguration2 = parametersUpgradeBySlotDeploymentExtensionConfiguration2.category('extension-configuration') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentExtensionConfiguration2.command('extension-configuration') + addparametersUpgradeBySlotDeploymentExtensionConfiguration2.command('add') .description($('Add extension-configuration in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionConfiguration" : {\r\n "allRoles":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "namedRoles":[\r\n {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7579,9 +7579,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentAllRoles0 = catparametersUpgradeBySlotDeploymentAllRoles0.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeBySlotDeploymentAllRoles0 = parametersUpgradeBySlotDeploymentAllRoles0.category('set') + var setparametersUpgradeBySlotDeploymentAllRoles0 = parametersUpgradeBySlotDeploymentAllRoles0.category('all-roles') .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); - setparametersUpgradeBySlotDeploymentAllRoles0.command('all-roles') + setparametersUpgradeBySlotDeploymentAllRoles0.command('set') .description($('Set all-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7643,9 +7643,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentAllRoles1 = catparametersUpgradeBySlotDeploymentAllRoles1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentAllRoles1 = parametersUpgradeBySlotDeploymentAllRoles1.category('remove') + var removeparametersUpgradeBySlotDeploymentAllRoles1 = parametersUpgradeBySlotDeploymentAllRoles1.category('all-roles') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentAllRoles1.command('all-roles') + removeparametersUpgradeBySlotDeploymentAllRoles1.command('remove') .description($('Remove all-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7693,9 +7693,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentAllRoles2 = catparametersUpgradeBySlotDeploymentAllRoles2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentAllRoles2 = parametersUpgradeBySlotDeploymentAllRoles2.category('add') + var addparametersUpgradeBySlotDeploymentAllRoles2 = parametersUpgradeBySlotDeploymentAllRoles2.category('all-roles') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentAllRoles2.command('all-roles') + addparametersUpgradeBySlotDeploymentAllRoles2.command('add') .description($('Add all-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "allRoles" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7756,9 +7756,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentNamedRoles0 = catparametersUpgradeBySlotDeploymentNamedRoles0.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeBySlotDeploymentNamedRoles0 = parametersUpgradeBySlotDeploymentNamedRoles0.category('set') + var setparametersUpgradeBySlotDeploymentNamedRoles0 = parametersUpgradeBySlotDeploymentNamedRoles0.category('named-roles') .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); - setparametersUpgradeBySlotDeploymentNamedRoles0.command('named-roles') + setparametersUpgradeBySlotDeploymentNamedRoles0.command('set') .description($('Set named-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7820,9 +7820,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentNamedRoles1 = catparametersUpgradeBySlotDeploymentNamedRoles1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentNamedRoles1 = parametersUpgradeBySlotDeploymentNamedRoles1.category('remove') + var removeparametersUpgradeBySlotDeploymentNamedRoles1 = parametersUpgradeBySlotDeploymentNamedRoles1.category('named-roles') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentNamedRoles1.command('named-roles') + removeparametersUpgradeBySlotDeploymentNamedRoles1.command('remove') .description($('Remove named-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7870,9 +7870,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentNamedRoles2 = catparametersUpgradeBySlotDeploymentNamedRoles2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentNamedRoles2 = parametersUpgradeBySlotDeploymentNamedRoles2.category('add') + var addparametersUpgradeBySlotDeploymentNamedRoles2 = parametersUpgradeBySlotDeploymentNamedRoles2.category('named-roles') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentNamedRoles2.command('named-roles') + addparametersUpgradeBySlotDeploymentNamedRoles2.command('add') .description($('Add named-roles in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "namedRoles" : {\r\n "extensions":[\r\n {\r\n "id":"",\r\n "state":""\r\n }\r\n ],\r\n "roleName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7933,9 +7933,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentExtensions0 = catparametersUpgradeBySlotDeploymentExtensions0.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersUpgradeBySlotDeploymentExtensions0 = parametersUpgradeBySlotDeploymentExtensions0.category('set') + var setparametersUpgradeBySlotDeploymentExtensions0 = parametersUpgradeBySlotDeploymentExtensions0.category('extensions') .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); - setparametersUpgradeBySlotDeploymentExtensions0.command('extensions') + setparametersUpgradeBySlotDeploymentExtensions0.command('set') .description($('Set extensions in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -7976,9 +7976,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentExtensions1 = catparametersUpgradeBySlotDeploymentExtensions1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentExtensions1 = parametersUpgradeBySlotDeploymentExtensions1.category('remove') + var removeparametersUpgradeBySlotDeploymentExtensions1 = parametersUpgradeBySlotDeploymentExtensions1.category('extensions') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentExtensions1.command('extensions') + removeparametersUpgradeBySlotDeploymentExtensions1.command('remove') .description($('Remove extensions in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8011,9 +8011,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentExtensions2 = catparametersUpgradeBySlotDeploymentExtensions2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentExtensions2 = parametersUpgradeBySlotDeploymentExtensions2.category('add') + var addparametersUpgradeBySlotDeploymentExtensions2 = parametersUpgradeBySlotDeploymentExtensions2.category('extensions') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentExtensions2.command('extensions') + addparametersUpgradeBySlotDeploymentExtensions2.command('add') .description($('Add extensions in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensions" : {\r\n "id":"",\r\n "state":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8052,9 +8052,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentMode1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentMode1 = catparametersUpgradeBySlotDeploymentMode1.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersUpgradeBySlotDeploymentMode1 = parametersUpgradeBySlotDeploymentMode1.category('remove') + var removeparametersUpgradeBySlotDeploymentMode1 = parametersUpgradeBySlotDeploymentMode1.category('mode') .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); - removeparametersUpgradeBySlotDeploymentMode1.command('mode') + removeparametersUpgradeBySlotDeploymentMode1.command('remove') .description($('Remove mode in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8084,9 +8084,9 @@ exports.init = function (cli) { var catparametersUpgradeBySlotDeploymentMode2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersUpgradeBySlotDeploymentMode2 = catparametersUpgradeBySlotDeploymentMode2.category('upgrade-by-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersUpgradeBySlotDeploymentMode2 = parametersUpgradeBySlotDeploymentMode2.category('add') + var addparametersUpgradeBySlotDeploymentMode2 = parametersUpgradeBySlotDeploymentMode2.category('mode') .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); - addparametersUpgradeBySlotDeploymentMode2.command('mode') + addparametersUpgradeBySlotDeploymentMode2.command('add') .description($('Add mode in upgrade-by-slot-parameters string or files, e.g. \r\n {\r\n ...\r\n "mode" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8238,9 +8238,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0 = catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.category('walk-upgrade-domain-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.category('set') + var setparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to set components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); - setparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.command('deployment-walk-upgrade-domain-parameters') + setparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.command('set') .description($('Set deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8286,9 +8286,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1 = catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.category('walk-upgrade-domain-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.category('remove') + var removeparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to remove components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); - removeparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.command('deployment-walk-upgrade-domain-parameters') + removeparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.command('remove') .description($('Remove deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8330,9 +8330,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2 = catparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.category('walk-upgrade-domain-by-deployment-name-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.category('add') + var addparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2 = parametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to add components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); - addparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.command('deployment-walk-upgrade-domain-parameters') + addparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.command('add') .description($('Add deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-name-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8495,9 +8495,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0 = catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0.category('walk-upgrade-domain-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var setparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0.category('set') + var setparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to set components of deployment in walk-upgrade-domain-by-deployment-slot-parameters file.')); - setparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0.command('deployment-walk-upgrade-domain-parameters') + setparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters0.command('set') .description($('Set deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8543,9 +8543,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1 = catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1.category('walk-upgrade-domain-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var removeparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1.category('remove') + var removeparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to remove components of deployment in walk-upgrade-domain-by-deployment-slot-parameters file.')); - removeparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1.command('deployment-walk-upgrade-domain-parameters') + removeparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters1.command('remove') .description($('Remove deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8587,9 +8587,9 @@ exports.init = function (cli) { var catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2 = catparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2.category('walk-upgrade-domain-by-deployment-slot-parameters') .description($('Commands to manage configuration of deployment in the parameter file.')); - var addparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2.category('add') + var addparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2 = parametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2.category('deployment-walk-upgrade-domain-parameters') .description($('Commands to add components of deployment in walk-upgrade-domain-by-deployment-slot-parameters file.')); - addparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2.command('deployment-walk-upgrade-domain-parameters') + addparametersWalkUpgradeDomainByDeploymentSlotDeploymentDeploymentWalkUpgradeDomainParameters2.command('add') .description($('Add deployment-walk-upgrade-domain-parameters in walk-upgrade-domain-by-deployment-slot-parameters string or files, e.g. \r\n{\r\n "upgradeDomain":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -8952,9 +8952,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageExtensionImageRegisterParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageExtensionImageRegisterParameters0 = catparametersRegisterExtensionImageExtensionImageRegisterParameters0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageExtensionImageRegisterParameters0 = parametersRegisterExtensionImageExtensionImageRegisterParameters0.category('set') + var setparametersRegisterExtensionImageExtensionImageRegisterParameters0 = parametersRegisterExtensionImageExtensionImageRegisterParameters0.category('extension-image-register-parameters') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageExtensionImageRegisterParameters0.command('extension-image-register-parameters') + setparametersRegisterExtensionImageExtensionImageRegisterParameters0.command('set') .description($('Set extension-image-register-parameters in register-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -9280,9 +9280,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageExtensionImageRegisterParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageExtensionImageRegisterParameters1 = catparametersRegisterExtensionImageExtensionImageRegisterParameters1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageExtensionImageRegisterParameters1 = parametersRegisterExtensionImageExtensionImageRegisterParameters1.category('remove') + var removeparametersRegisterExtensionImageExtensionImageRegisterParameters1 = parametersRegisterExtensionImageExtensionImageRegisterParameters1.category('extension-image-register-parameters') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageExtensionImageRegisterParameters1.command('extension-image-register-parameters') + removeparametersRegisterExtensionImageExtensionImageRegisterParameters1.command('remove') .description($('Remove extension-image-register-parameters in register-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -9449,9 +9449,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageExtensionImageRegisterParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageExtensionImageRegisterParameters2 = catparametersRegisterExtensionImageExtensionImageRegisterParameters2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageExtensionImageRegisterParameters2 = parametersRegisterExtensionImageExtensionImageRegisterParameters2.category('add') + var addparametersRegisterExtensionImageExtensionImageRegisterParameters2 = parametersRegisterExtensionImageExtensionImageRegisterParameters2.category('extension-image-register-parameters') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageExtensionImageRegisterParameters2.command('extension-image-register-parameters') + addparametersRegisterExtensionImageExtensionImageRegisterParameters2.command('add') .description($('Add extension-image-register-parameters in register-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -9781,9 +9781,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageCertificate0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageCertificate0 = catparametersRegisterExtensionImageCertificate0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageCertificate0 = parametersRegisterExtensionImageCertificate0.category('set') + var setparametersRegisterExtensionImageCertificate0 = parametersRegisterExtensionImageCertificate0.category('certificate') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageCertificate0.command('certificate') + setparametersRegisterExtensionImageCertificate0.command('set') .description($('Set certificate in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -9863,9 +9863,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageCertificate1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageCertificate1 = catparametersRegisterExtensionImageCertificate1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageCertificate1 = parametersRegisterExtensionImageCertificate1.category('remove') + var removeparametersRegisterExtensionImageCertificate1 = parametersRegisterExtensionImageCertificate1.category('certificate') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageCertificate1.command('certificate') + removeparametersRegisterExtensionImageCertificate1.command('remove') .description($('Remove certificate in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -9922,9 +9922,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageCertificate2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageCertificate2 = catparametersRegisterExtensionImageCertificate2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageCertificate2 = parametersRegisterExtensionImageCertificate2.category('add') + var addparametersRegisterExtensionImageCertificate2 = parametersRegisterExtensionImageCertificate2.category('certificate') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageCertificate2.command('certificate') + addparametersRegisterExtensionImageCertificate2.command('add') .description($('Add certificate in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10008,9 +10008,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageExtensionEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageExtensionEndpoints1 = catparametersRegisterExtensionImageExtensionEndpoints1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageExtensionEndpoints1 = parametersRegisterExtensionImageExtensionEndpoints1.category('remove') + var removeparametersRegisterExtensionImageExtensionEndpoints1 = parametersRegisterExtensionImageExtensionEndpoints1.category('extension-endpoints') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageExtensionEndpoints1.command('extension-endpoints') + removeparametersRegisterExtensionImageExtensionEndpoints1.command('remove') .description($('Remove extension-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionEndpoints" : {\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10062,9 +10062,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageExtensionEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageExtensionEndpoints2 = catparametersRegisterExtensionImageExtensionEndpoints2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageExtensionEndpoints2 = parametersRegisterExtensionImageExtensionEndpoints2.category('add') + var addparametersRegisterExtensionImageExtensionEndpoints2 = parametersRegisterExtensionImageExtensionEndpoints2.category('extension-endpoints') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageExtensionEndpoints2.command('extension-endpoints') + addparametersRegisterExtensionImageExtensionEndpoints2.command('add') .description($('Add extension-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionEndpoints" : {\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10136,9 +10136,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInputEndpoints0 = catparametersRegisterExtensionImageInputEndpoints0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageInputEndpoints0 = parametersRegisterExtensionImageInputEndpoints0.category('set') + var setparametersRegisterExtensionImageInputEndpoints0 = parametersRegisterExtensionImageInputEndpoints0.category('input-endpoints') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageInputEndpoints0.command('input-endpoints') + setparametersRegisterExtensionImageInputEndpoints0.command('set') .description($('Set input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10222,9 +10222,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInputEndpoints1 = catparametersRegisterExtensionImageInputEndpoints1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageInputEndpoints1 = parametersRegisterExtensionImageInputEndpoints1.category('remove') + var removeparametersRegisterExtensionImageInputEndpoints1 = parametersRegisterExtensionImageInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageInputEndpoints1.command('input-endpoints') + removeparametersRegisterExtensionImageInputEndpoints1.command('remove') .description($('Remove input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10282,9 +10282,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInputEndpoints2 = catparametersRegisterExtensionImageInputEndpoints2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageInputEndpoints2 = parametersRegisterExtensionImageInputEndpoints2.category('add') + var addparametersRegisterExtensionImageInputEndpoints2 = parametersRegisterExtensionImageInputEndpoints2.category('input-endpoints') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageInputEndpoints2.command('input-endpoints') + addparametersRegisterExtensionImageInputEndpoints2.command('add') .description($('Add input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10367,9 +10367,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInstanceInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInstanceInputEndpoints0 = catparametersRegisterExtensionImageInstanceInputEndpoints0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageInstanceInputEndpoints0 = parametersRegisterExtensionImageInstanceInputEndpoints0.category('set') + var setparametersRegisterExtensionImageInstanceInputEndpoints0 = parametersRegisterExtensionImageInstanceInputEndpoints0.category('instance-input-endpoints') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageInstanceInputEndpoints0.command('instance-input-endpoints') + setparametersRegisterExtensionImageInstanceInputEndpoints0.command('set') .description($('Set instance-input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10464,9 +10464,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInstanceInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInstanceInputEndpoints1 = catparametersRegisterExtensionImageInstanceInputEndpoints1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageInstanceInputEndpoints1 = parametersRegisterExtensionImageInstanceInputEndpoints1.category('remove') + var removeparametersRegisterExtensionImageInstanceInputEndpoints1 = parametersRegisterExtensionImageInstanceInputEndpoints1.category('instance-input-endpoints') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageInstanceInputEndpoints1.command('instance-input-endpoints') + removeparametersRegisterExtensionImageInstanceInputEndpoints1.command('remove') .description($('Remove instance-input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10529,9 +10529,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInstanceInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInstanceInputEndpoints2 = catparametersRegisterExtensionImageInstanceInputEndpoints2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageInstanceInputEndpoints2 = parametersRegisterExtensionImageInstanceInputEndpoints2.category('add') + var addparametersRegisterExtensionImageInstanceInputEndpoints2 = parametersRegisterExtensionImageInstanceInputEndpoints2.category('instance-input-endpoints') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageInstanceInputEndpoints2.command('instance-input-endpoints') + addparametersRegisterExtensionImageInstanceInputEndpoints2.command('add') .description($('Add instance-input-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10625,9 +10625,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInternalEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInternalEndpoints0 = catparametersRegisterExtensionImageInternalEndpoints0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageInternalEndpoints0 = parametersRegisterExtensionImageInternalEndpoints0.category('set') + var setparametersRegisterExtensionImageInternalEndpoints0 = parametersRegisterExtensionImageInternalEndpoints0.category('internal-endpoints') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageInternalEndpoints0.command('internal-endpoints') + setparametersRegisterExtensionImageInternalEndpoints0.command('set') .description($('Set internal-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10700,9 +10700,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInternalEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInternalEndpoints1 = catparametersRegisterExtensionImageInternalEndpoints1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageInternalEndpoints1 = parametersRegisterExtensionImageInternalEndpoints1.category('remove') + var removeparametersRegisterExtensionImageInternalEndpoints1 = parametersRegisterExtensionImageInternalEndpoints1.category('internal-endpoints') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageInternalEndpoints1.command('internal-endpoints') + removeparametersRegisterExtensionImageInternalEndpoints1.command('remove') .description($('Remove internal-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10755,9 +10755,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageInternalEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageInternalEndpoints2 = catparametersRegisterExtensionImageInternalEndpoints2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageInternalEndpoints2 = parametersRegisterExtensionImageInternalEndpoints2.category('add') + var addparametersRegisterExtensionImageInternalEndpoints2 = parametersRegisterExtensionImageInternalEndpoints2.category('internal-endpoints') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageInternalEndpoints2.command('internal-endpoints') + addparametersRegisterExtensionImageInternalEndpoints2.command('add') .description($('Add internal-endpoints in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10829,9 +10829,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageLocalResources0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageLocalResources0 = catparametersRegisterExtensionImageLocalResources0.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersRegisterExtensionImageLocalResources0 = parametersRegisterExtensionImageLocalResources0.category('set') + var setparametersRegisterExtensionImageLocalResources0 = parametersRegisterExtensionImageLocalResources0.category('local-resources') .description($('Commands to set components of extension-image in register-parameters file.')); - setparametersRegisterExtensionImageLocalResources0.command('local-resources') + setparametersRegisterExtensionImageLocalResources0.command('set') .description($('Set local-resources in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10893,9 +10893,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageLocalResources1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageLocalResources1 = catparametersRegisterExtensionImageLocalResources1.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersRegisterExtensionImageLocalResources1 = parametersRegisterExtensionImageLocalResources1.category('remove') + var removeparametersRegisterExtensionImageLocalResources1 = parametersRegisterExtensionImageLocalResources1.category('local-resources') .description($('Commands to remove components of extension-image in register-parameters file.')); - removeparametersRegisterExtensionImageLocalResources1.command('local-resources') + removeparametersRegisterExtensionImageLocalResources1.command('remove') .description($('Remove local-resources in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -10943,9 +10943,9 @@ exports.init = function (cli) { var catparametersRegisterExtensionImageLocalResources2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersRegisterExtensionImageLocalResources2 = catparametersRegisterExtensionImageLocalResources2.category('register-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersRegisterExtensionImageLocalResources2 = parametersRegisterExtensionImageLocalResources2.category('add') + var addparametersRegisterExtensionImageLocalResources2 = parametersRegisterExtensionImageLocalResources2.category('local-resources') .description($('Commands to add components of extension-image in register-parameters file.')); - addparametersRegisterExtensionImageLocalResources2.command('local-resources') + addparametersRegisterExtensionImageLocalResources2.command('add') .description($('Add local-resources in register-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -11204,9 +11204,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageExtensionImageUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageExtensionImageUpdateParameters0 = catparametersUpdateExtensionImageExtensionImageUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageExtensionImageUpdateParameters0 = parametersUpdateExtensionImageExtensionImageUpdateParameters0.category('set') + var setparametersUpdateExtensionImageExtensionImageUpdateParameters0 = parametersUpdateExtensionImageExtensionImageUpdateParameters0.category('extension-image-update-parameters') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageExtensionImageUpdateParameters0.command('extension-image-update-parameters') + setparametersUpdateExtensionImageExtensionImageUpdateParameters0.command('set') .description($('Set extension-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -11532,9 +11532,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageExtensionImageUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageExtensionImageUpdateParameters1 = catparametersUpdateExtensionImageExtensionImageUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageExtensionImageUpdateParameters1 = parametersUpdateExtensionImageExtensionImageUpdateParameters1.category('remove') + var removeparametersUpdateExtensionImageExtensionImageUpdateParameters1 = parametersUpdateExtensionImageExtensionImageUpdateParameters1.category('extension-image-update-parameters') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageExtensionImageUpdateParameters1.command('extension-image-update-parameters') + removeparametersUpdateExtensionImageExtensionImageUpdateParameters1.command('remove') .description($('Remove extension-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -11701,9 +11701,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageExtensionImageUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageExtensionImageUpdateParameters2 = catparametersUpdateExtensionImageExtensionImageUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageExtensionImageUpdateParameters2 = parametersUpdateExtensionImageExtensionImageUpdateParameters2.category('add') + var addparametersUpdateExtensionImageExtensionImageUpdateParameters2 = parametersUpdateExtensionImageExtensionImageUpdateParameters2.category('extension-image-update-parameters') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageExtensionImageUpdateParameters2.command('extension-image-update-parameters') + addparametersUpdateExtensionImageExtensionImageUpdateParameters2.command('add') .description($('Add extension-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "blockRoleUponFailure":null,\r\n "certificate":{\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n },\r\n "companyName":"",\r\n "description":"",\r\n "disallowMajorVersionUpgrade":null,\r\n "eula":"",\r\n "extensionEndpoints":{\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n },\r\n "homepageUri":"",\r\n "hostingResources":"",\r\n "isInternalExtension":null,\r\n "isJsonExtension":null,\r\n "label":"",\r\n "localResources":[\r\n {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ],\r\n "mediaLink":"",\r\n "privacyUri":"",\r\n "privateConfigurationSchema":"",\r\n "providerNameSpace":"",\r\n "publicConfigurationSchema":"",\r\n "publishedDate":null,\r\n "publisherName":"",\r\n "regions":"",\r\n "replicationCompleted":null,\r\n "sampleConfig":"",\r\n "supportedOS":"",\r\n "type":"",\r\n "version":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12033,9 +12033,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageCertificate0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageCertificate0 = catparametersUpdateExtensionImageCertificate0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageCertificate0 = parametersUpdateExtensionImageCertificate0.category('set') + var setparametersUpdateExtensionImageCertificate0 = parametersUpdateExtensionImageCertificate0.category('certificate') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageCertificate0.command('certificate') + setparametersUpdateExtensionImageCertificate0.command('set') .description($('Set certificate in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12115,9 +12115,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageCertificate1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageCertificate1 = catparametersUpdateExtensionImageCertificate1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageCertificate1 = parametersUpdateExtensionImageCertificate1.category('remove') + var removeparametersUpdateExtensionImageCertificate1 = parametersUpdateExtensionImageCertificate1.category('certificate') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageCertificate1.command('certificate') + removeparametersUpdateExtensionImageCertificate1.command('remove') .description($('Remove certificate in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12174,9 +12174,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageCertificate2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageCertificate2 = catparametersUpdateExtensionImageCertificate2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageCertificate2 = parametersUpdateExtensionImageCertificate2.category('add') + var addparametersUpdateExtensionImageCertificate2 = parametersUpdateExtensionImageCertificate2.category('certificate') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageCertificate2.command('certificate') + addparametersUpdateExtensionImageCertificate2.command('add') .description($('Add certificate in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificate" : {\r\n "storeLocation":"",\r\n "storeName":"",\r\n "thumbprintAlgorithm":"",\r\n "thumbprintRequired":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12260,9 +12260,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageExtensionEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageExtensionEndpoints1 = catparametersUpdateExtensionImageExtensionEndpoints1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageExtensionEndpoints1 = parametersUpdateExtensionImageExtensionEndpoints1.category('remove') + var removeparametersUpdateExtensionImageExtensionEndpoints1 = parametersUpdateExtensionImageExtensionEndpoints1.category('extension-endpoints') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageExtensionEndpoints1.command('extension-endpoints') + removeparametersUpdateExtensionImageExtensionEndpoints1.command('remove') .description($('Remove extension-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionEndpoints" : {\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12314,9 +12314,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageExtensionEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageExtensionEndpoints2 = catparametersUpdateExtensionImageExtensionEndpoints2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageExtensionEndpoints2 = parametersUpdateExtensionImageExtensionEndpoints2.category('add') + var addparametersUpdateExtensionImageExtensionEndpoints2 = parametersUpdateExtensionImageExtensionEndpoints2.category('extension-endpoints') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageExtensionEndpoints2.command('extension-endpoints') + addparametersUpdateExtensionImageExtensionEndpoints2.command('add') .description($('Add extension-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "extensionEndpoints" : {\r\n "inputEndpoints":[\r\n {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ],\r\n "instanceInputEndpoints":[\r\n {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ],\r\n "internalEndpoints":[\r\n {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12388,9 +12388,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInputEndpoints0 = catparametersUpdateExtensionImageInputEndpoints0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageInputEndpoints0 = parametersUpdateExtensionImageInputEndpoints0.category('set') + var setparametersUpdateExtensionImageInputEndpoints0 = parametersUpdateExtensionImageInputEndpoints0.category('input-endpoints') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageInputEndpoints0.command('input-endpoints') + setparametersUpdateExtensionImageInputEndpoints0.command('set') .description($('Set input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12474,9 +12474,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInputEndpoints1 = catparametersUpdateExtensionImageInputEndpoints1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageInputEndpoints1 = parametersUpdateExtensionImageInputEndpoints1.category('remove') + var removeparametersUpdateExtensionImageInputEndpoints1 = parametersUpdateExtensionImageInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageInputEndpoints1.command('input-endpoints') + removeparametersUpdateExtensionImageInputEndpoints1.command('remove') .description($('Remove input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12534,9 +12534,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInputEndpoints2 = catparametersUpdateExtensionImageInputEndpoints2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageInputEndpoints2 = parametersUpdateExtensionImageInputEndpoints2.category('add') + var addparametersUpdateExtensionImageInputEndpoints2 = parametersUpdateExtensionImageInputEndpoints2.category('input-endpoints') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageInputEndpoints2.command('input-endpoints') + addparametersUpdateExtensionImageInputEndpoints2.command('add') .description($('Add input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "localPort":"",\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12619,9 +12619,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInstanceInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInstanceInputEndpoints0 = catparametersUpdateExtensionImageInstanceInputEndpoints0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageInstanceInputEndpoints0 = parametersUpdateExtensionImageInstanceInputEndpoints0.category('set') + var setparametersUpdateExtensionImageInstanceInputEndpoints0 = parametersUpdateExtensionImageInstanceInputEndpoints0.category('instance-input-endpoints') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageInstanceInputEndpoints0.command('instance-input-endpoints') + setparametersUpdateExtensionImageInstanceInputEndpoints0.command('set') .description($('Set instance-input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12716,9 +12716,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInstanceInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInstanceInputEndpoints1 = catparametersUpdateExtensionImageInstanceInputEndpoints1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageInstanceInputEndpoints1 = parametersUpdateExtensionImageInstanceInputEndpoints1.category('remove') + var removeparametersUpdateExtensionImageInstanceInputEndpoints1 = parametersUpdateExtensionImageInstanceInputEndpoints1.category('instance-input-endpoints') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageInstanceInputEndpoints1.command('instance-input-endpoints') + removeparametersUpdateExtensionImageInstanceInputEndpoints1.command('remove') .description($('Remove instance-input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12781,9 +12781,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInstanceInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInstanceInputEndpoints2 = catparametersUpdateExtensionImageInstanceInputEndpoints2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageInstanceInputEndpoints2 = parametersUpdateExtensionImageInstanceInputEndpoints2.category('add') + var addparametersUpdateExtensionImageInstanceInputEndpoints2 = parametersUpdateExtensionImageInstanceInputEndpoints2.category('instance-input-endpoints') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageInstanceInputEndpoints2.command('instance-input-endpoints') + addparametersUpdateExtensionImageInstanceInputEndpoints2.command('add') .description($('Add instance-input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "instanceInputEndpoints" : {\r\n "fixedPortMax":0,\r\n "fixedPortMin":0,\r\n "localPort":"",\r\n "name":"",\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12877,9 +12877,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInternalEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInternalEndpoints0 = catparametersUpdateExtensionImageInternalEndpoints0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageInternalEndpoints0 = parametersUpdateExtensionImageInternalEndpoints0.category('set') + var setparametersUpdateExtensionImageInternalEndpoints0 = parametersUpdateExtensionImageInternalEndpoints0.category('internal-endpoints') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageInternalEndpoints0.command('internal-endpoints') + setparametersUpdateExtensionImageInternalEndpoints0.command('set') .description($('Set internal-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -12952,9 +12952,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInternalEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInternalEndpoints1 = catparametersUpdateExtensionImageInternalEndpoints1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageInternalEndpoints1 = parametersUpdateExtensionImageInternalEndpoints1.category('remove') + var removeparametersUpdateExtensionImageInternalEndpoints1 = parametersUpdateExtensionImageInternalEndpoints1.category('internal-endpoints') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageInternalEndpoints1.command('internal-endpoints') + removeparametersUpdateExtensionImageInternalEndpoints1.command('remove') .description($('Remove internal-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13007,9 +13007,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageInternalEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageInternalEndpoints2 = catparametersUpdateExtensionImageInternalEndpoints2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageInternalEndpoints2 = parametersUpdateExtensionImageInternalEndpoints2.category('add') + var addparametersUpdateExtensionImageInternalEndpoints2 = parametersUpdateExtensionImageInternalEndpoints2.category('internal-endpoints') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageInternalEndpoints2.command('internal-endpoints') + addparametersUpdateExtensionImageInternalEndpoints2.command('add') .description($('Add internal-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "internalEndpoints" : {\r\n "name":"",\r\n "port":0,\r\n "protocol":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13081,9 +13081,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageLocalResources0 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageLocalResources0 = catparametersUpdateExtensionImageLocalResources0.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var setparametersUpdateExtensionImageLocalResources0 = parametersUpdateExtensionImageLocalResources0.category('set') + var setparametersUpdateExtensionImageLocalResources0 = parametersUpdateExtensionImageLocalResources0.category('local-resources') .description($('Commands to set components of extension-image in update-parameters file.')); - setparametersUpdateExtensionImageLocalResources0.command('local-resources') + setparametersUpdateExtensionImageLocalResources0.command('set') .description($('Set local-resources in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13145,9 +13145,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageLocalResources1 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageLocalResources1 = catparametersUpdateExtensionImageLocalResources1.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var removeparametersUpdateExtensionImageLocalResources1 = parametersUpdateExtensionImageLocalResources1.category('remove') + var removeparametersUpdateExtensionImageLocalResources1 = parametersUpdateExtensionImageLocalResources1.category('local-resources') .description($('Commands to remove components of extension-image in update-parameters file.')); - removeparametersUpdateExtensionImageLocalResources1.command('local-resources') + removeparametersUpdateExtensionImageLocalResources1.command('remove') .description($('Remove local-resources in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13195,9 +13195,9 @@ exports.init = function (cli) { var catparametersUpdateExtensionImageLocalResources2 = cli.category('invoke').description('Commands to invoke service management operations.').category('extension-image'); var parametersUpdateExtensionImageLocalResources2 = catparametersUpdateExtensionImageLocalResources2.category('update-parameters') .description($('Commands to manage configuration of extension-image in the parameter file.')); - var addparametersUpdateExtensionImageLocalResources2 = parametersUpdateExtensionImageLocalResources2.category('add') + var addparametersUpdateExtensionImageLocalResources2 = parametersUpdateExtensionImageLocalResources2.category('local-resources') .description($('Commands to add components of extension-image in update-parameters file.')); - addparametersUpdateExtensionImageLocalResources2.command('local-resources') + addparametersUpdateExtensionImageLocalResources2.command('add') .description($('Add local-resources in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "localResources" : {\r\n "name":"",\r\n "sizeInMB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13460,9 +13460,9 @@ exports.init = function (cli) { var catparametersCreateHostedServiceHostedServiceCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersCreateHostedServiceHostedServiceCreateParameters0 = catparametersCreateHostedServiceHostedServiceCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var setparametersCreateHostedServiceHostedServiceCreateParameters0 = parametersCreateHostedServiceHostedServiceCreateParameters0.category('set') + var setparametersCreateHostedServiceHostedServiceCreateParameters0 = parametersCreateHostedServiceHostedServiceCreateParameters0.category('hosted-service-create-parameters') .description($('Commands to set components of hosted-service in create-parameters file.')); - setparametersCreateHostedServiceHostedServiceCreateParameters0.command('hosted-service-create-parameters') + setparametersCreateHostedServiceHostedServiceCreateParameters0.command('set') .description($('Set hosted-service-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "affinityGroup":"",\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "location":"",\r\n "reverseDnsFqdn":"",\r\n "serviceName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13574,9 +13574,9 @@ exports.init = function (cli) { var catparametersCreateHostedServiceHostedServiceCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersCreateHostedServiceHostedServiceCreateParameters1 = catparametersCreateHostedServiceHostedServiceCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var removeparametersCreateHostedServiceHostedServiceCreateParameters1 = parametersCreateHostedServiceHostedServiceCreateParameters1.category('remove') + var removeparametersCreateHostedServiceHostedServiceCreateParameters1 = parametersCreateHostedServiceHostedServiceCreateParameters1.category('hosted-service-create-parameters') .description($('Commands to remove components of hosted-service in create-parameters file.')); - removeparametersCreateHostedServiceHostedServiceCreateParameters1.command('hosted-service-create-parameters') + removeparametersCreateHostedServiceHostedServiceCreateParameters1.command('remove') .description($('Remove hosted-service-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "affinityGroup":"",\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "location":"",\r\n "reverseDnsFqdn":"",\r\n "serviceName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -13648,9 +13648,9 @@ exports.init = function (cli) { var catparametersCreateHostedServiceHostedServiceCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersCreateHostedServiceHostedServiceCreateParameters2 = catparametersCreateHostedServiceHostedServiceCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var addparametersCreateHostedServiceHostedServiceCreateParameters2 = parametersCreateHostedServiceHostedServiceCreateParameters2.category('add') + var addparametersCreateHostedServiceHostedServiceCreateParameters2 = parametersCreateHostedServiceHostedServiceCreateParameters2.category('hosted-service-create-parameters') .description($('Commands to add components of hosted-service in create-parameters file.')); - addparametersCreateHostedServiceHostedServiceCreateParameters2.command('hosted-service-create-parameters') + addparametersCreateHostedServiceHostedServiceCreateParameters2.command('add') .description($('Add hosted-service-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "affinityGroup":"",\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "location":"",\r\n "reverseDnsFqdn":"",\r\n "serviceName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14151,9 +14151,9 @@ exports.init = function (cli) { var catparametersUpdateHostedServiceHostedServiceUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersUpdateHostedServiceHostedServiceUpdateParameters0 = catparametersUpdateHostedServiceHostedServiceUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var setparametersUpdateHostedServiceHostedServiceUpdateParameters0 = parametersUpdateHostedServiceHostedServiceUpdateParameters0.category('set') + var setparametersUpdateHostedServiceHostedServiceUpdateParameters0 = parametersUpdateHostedServiceHostedServiceUpdateParameters0.category('hosted-service-update-parameters') .description($('Commands to set components of hosted-service in update-parameters file.')); - setparametersUpdateHostedServiceHostedServiceUpdateParameters0.command('hosted-service-update-parameters') + setparametersUpdateHostedServiceHostedServiceUpdateParameters0.command('set') .description($('Set hosted-service-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "reverseDnsFqdn":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14232,9 +14232,9 @@ exports.init = function (cli) { var catparametersUpdateHostedServiceHostedServiceUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersUpdateHostedServiceHostedServiceUpdateParameters1 = catparametersUpdateHostedServiceHostedServiceUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var removeparametersUpdateHostedServiceHostedServiceUpdateParameters1 = parametersUpdateHostedServiceHostedServiceUpdateParameters1.category('remove') + var removeparametersUpdateHostedServiceHostedServiceUpdateParameters1 = parametersUpdateHostedServiceHostedServiceUpdateParameters1.category('hosted-service-update-parameters') .description($('Commands to remove components of hosted-service in update-parameters file.')); - removeparametersUpdateHostedServiceHostedServiceUpdateParameters1.command('hosted-service-update-parameters') + removeparametersUpdateHostedServiceHostedServiceUpdateParameters1.command('remove') .description($('Remove hosted-service-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "reverseDnsFqdn":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14291,9 +14291,9 @@ exports.init = function (cli) { var catparametersUpdateHostedServiceHostedServiceUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('hosted-service'); var parametersUpdateHostedServiceHostedServiceUpdateParameters2 = catparametersUpdateHostedServiceHostedServiceUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of hosted-service in the parameter file.')); - var addparametersUpdateHostedServiceHostedServiceUpdateParameters2 = parametersUpdateHostedServiceHostedServiceUpdateParameters2.category('add') + var addparametersUpdateHostedServiceHostedServiceUpdateParameters2 = parametersUpdateHostedServiceHostedServiceUpdateParameters2.category('hosted-service-update-parameters') .description($('Commands to add components of hosted-service in update-parameters file.')); - addparametersUpdateHostedServiceHostedServiceUpdateParameters2.command('hosted-service-update-parameters') + addparametersUpdateHostedServiceHostedServiceUpdateParameters2.command('add') .description($('Add hosted-service-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "extendedProperties":{\r\n },\r\n "label":"",\r\n "reverseDnsFqdn":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14494,9 +14494,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerLoadBalancerCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerLoadBalancerCreateParameters0 = catparametersCreateLoadBalancerLoadBalancerCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var setparametersCreateLoadBalancerLoadBalancerCreateParameters0 = parametersCreateLoadBalancerLoadBalancerCreateParameters0.category('set') + var setparametersCreateLoadBalancerLoadBalancerCreateParameters0 = parametersCreateLoadBalancerLoadBalancerCreateParameters0.category('load-balancer-create-parameters') .description($('Commands to set components of load-balancer in create-parameters file.')); - setparametersCreateLoadBalancerLoadBalancerCreateParameters0.command('load-balancer-create-parameters') + setparametersCreateLoadBalancerLoadBalancerCreateParameters0.command('set') .description($('Set load-balancer-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14553,9 +14553,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerLoadBalancerCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerLoadBalancerCreateParameters1 = catparametersCreateLoadBalancerLoadBalancerCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var removeparametersCreateLoadBalancerLoadBalancerCreateParameters1 = parametersCreateLoadBalancerLoadBalancerCreateParameters1.category('remove') + var removeparametersCreateLoadBalancerLoadBalancerCreateParameters1 = parametersCreateLoadBalancerLoadBalancerCreateParameters1.category('load-balancer-create-parameters') .description($('Commands to remove components of load-balancer in create-parameters file.')); - removeparametersCreateLoadBalancerLoadBalancerCreateParameters1.command('load-balancer-create-parameters') + removeparametersCreateLoadBalancerLoadBalancerCreateParameters1.command('remove') .description($('Remove load-balancer-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14602,9 +14602,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerLoadBalancerCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerLoadBalancerCreateParameters2 = catparametersCreateLoadBalancerLoadBalancerCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var addparametersCreateLoadBalancerLoadBalancerCreateParameters2 = parametersCreateLoadBalancerLoadBalancerCreateParameters2.category('add') + var addparametersCreateLoadBalancerLoadBalancerCreateParameters2 = parametersCreateLoadBalancerLoadBalancerCreateParameters2.category('load-balancer-create-parameters') .description($('Commands to add components of load-balancer in create-parameters file.')); - addparametersCreateLoadBalancerLoadBalancerCreateParameters2.command('load-balancer-create-parameters') + addparametersCreateLoadBalancerLoadBalancerCreateParameters2.command('add') .description($('Add load-balancer-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14665,9 +14665,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerFrontendIPConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerFrontendIPConfiguration0 = catparametersCreateLoadBalancerFrontendIPConfiguration0.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var setparametersCreateLoadBalancerFrontendIPConfiguration0 = parametersCreateLoadBalancerFrontendIPConfiguration0.category('set') + var setparametersCreateLoadBalancerFrontendIPConfiguration0 = parametersCreateLoadBalancerFrontendIPConfiguration0.category('frontend-ip-configuration') .description($('Commands to set components of load-balancer in create-parameters file.')); - setparametersCreateLoadBalancerFrontendIPConfiguration0.command('frontend-ip-configuration') + setparametersCreateLoadBalancerFrontendIPConfiguration0.command('set') .description($('Set frontend-ip-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14735,9 +14735,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerFrontendIPConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerFrontendIPConfiguration1 = catparametersCreateLoadBalancerFrontendIPConfiguration1.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var removeparametersCreateLoadBalancerFrontendIPConfiguration1 = parametersCreateLoadBalancerFrontendIPConfiguration1.category('remove') + var removeparametersCreateLoadBalancerFrontendIPConfiguration1 = parametersCreateLoadBalancerFrontendIPConfiguration1.category('frontend-ip-configuration') .description($('Commands to remove components of load-balancer in create-parameters file.')); - removeparametersCreateLoadBalancerFrontendIPConfiguration1.command('frontend-ip-configuration') + removeparametersCreateLoadBalancerFrontendIPConfiguration1.command('remove') .description($('Remove frontend-ip-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -14789,9 +14789,9 @@ exports.init = function (cli) { var catparametersCreateLoadBalancerFrontendIPConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersCreateLoadBalancerFrontendIPConfiguration2 = catparametersCreateLoadBalancerFrontendIPConfiguration2.category('create-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var addparametersCreateLoadBalancerFrontendIPConfiguration2 = parametersCreateLoadBalancerFrontendIPConfiguration2.category('add') + var addparametersCreateLoadBalancerFrontendIPConfiguration2 = parametersCreateLoadBalancerFrontendIPConfiguration2.category('frontend-ip-configuration') .description($('Commands to add components of load-balancer in create-parameters file.')); - addparametersCreateLoadBalancerFrontendIPConfiguration2.command('frontend-ip-configuration') + addparametersCreateLoadBalancerFrontendIPConfiguration2.command('add') .description($('Add frontend-ip-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15027,9 +15027,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerLoadBalancerUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerLoadBalancerUpdateParameters0 = catparametersUpdateLoadBalancerLoadBalancerUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var setparametersUpdateLoadBalancerLoadBalancerUpdateParameters0 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters0.category('set') + var setparametersUpdateLoadBalancerLoadBalancerUpdateParameters0 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters0.category('load-balancer-update-parameters') .description($('Commands to set components of load-balancer in update-parameters file.')); - setparametersUpdateLoadBalancerLoadBalancerUpdateParameters0.command('load-balancer-update-parameters') + setparametersUpdateLoadBalancerLoadBalancerUpdateParameters0.command('set') .description($('Set load-balancer-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15086,9 +15086,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerLoadBalancerUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerLoadBalancerUpdateParameters1 = catparametersUpdateLoadBalancerLoadBalancerUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var removeparametersUpdateLoadBalancerLoadBalancerUpdateParameters1 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters1.category('remove') + var removeparametersUpdateLoadBalancerLoadBalancerUpdateParameters1 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters1.category('load-balancer-update-parameters') .description($('Commands to remove components of load-balancer in update-parameters file.')); - removeparametersUpdateLoadBalancerLoadBalancerUpdateParameters1.command('load-balancer-update-parameters') + removeparametersUpdateLoadBalancerLoadBalancerUpdateParameters1.command('remove') .description($('Remove load-balancer-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15135,9 +15135,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerLoadBalancerUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerLoadBalancerUpdateParameters2 = catparametersUpdateLoadBalancerLoadBalancerUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var addparametersUpdateLoadBalancerLoadBalancerUpdateParameters2 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters2.category('add') + var addparametersUpdateLoadBalancerLoadBalancerUpdateParameters2 = parametersUpdateLoadBalancerLoadBalancerUpdateParameters2.category('load-balancer-update-parameters') .description($('Commands to add components of load-balancer in update-parameters file.')); - addparametersUpdateLoadBalancerLoadBalancerUpdateParameters2.command('load-balancer-update-parameters') + addparametersUpdateLoadBalancerLoadBalancerUpdateParameters2.command('add') .description($('Add load-balancer-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15198,9 +15198,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerFrontendIPConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerFrontendIPConfiguration0 = catparametersUpdateLoadBalancerFrontendIPConfiguration0.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var setparametersUpdateLoadBalancerFrontendIPConfiguration0 = parametersUpdateLoadBalancerFrontendIPConfiguration0.category('set') + var setparametersUpdateLoadBalancerFrontendIPConfiguration0 = parametersUpdateLoadBalancerFrontendIPConfiguration0.category('frontend-ip-configuration') .description($('Commands to set components of load-balancer in update-parameters file.')); - setparametersUpdateLoadBalancerFrontendIPConfiguration0.command('frontend-ip-configuration') + setparametersUpdateLoadBalancerFrontendIPConfiguration0.command('set') .description($('Set frontend-ip-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15268,9 +15268,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerFrontendIPConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerFrontendIPConfiguration1 = catparametersUpdateLoadBalancerFrontendIPConfiguration1.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var removeparametersUpdateLoadBalancerFrontendIPConfiguration1 = parametersUpdateLoadBalancerFrontendIPConfiguration1.category('remove') + var removeparametersUpdateLoadBalancerFrontendIPConfiguration1 = parametersUpdateLoadBalancerFrontendIPConfiguration1.category('frontend-ip-configuration') .description($('Commands to remove components of load-balancer in update-parameters file.')); - removeparametersUpdateLoadBalancerFrontendIPConfiguration1.command('frontend-ip-configuration') + removeparametersUpdateLoadBalancerFrontendIPConfiguration1.command('remove') .description($('Remove frontend-ip-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15322,9 +15322,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancerFrontendIPConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('load-balancer'); var parametersUpdateLoadBalancerFrontendIPConfiguration2 = catparametersUpdateLoadBalancerFrontendIPConfiguration2.category('update-parameters') .description($('Commands to manage configuration of load-balancer in the parameter file.')); - var addparametersUpdateLoadBalancerFrontendIPConfiguration2 = parametersUpdateLoadBalancerFrontendIPConfiguration2.category('add') + var addparametersUpdateLoadBalancerFrontendIPConfiguration2 = parametersUpdateLoadBalancerFrontendIPConfiguration2.category('frontend-ip-configuration') .description($('Commands to add components of load-balancer in update-parameters file.')); - addparametersUpdateLoadBalancerFrontendIPConfiguration2.command('frontend-ip-configuration') + addparametersUpdateLoadBalancerFrontendIPConfiguration2.command('add') .description($('Add frontend-ip-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15540,9 +15540,9 @@ exports.init = function (cli) { var catparametersCreateServiceCertificateServiceCertificateCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('service-certificate'); var parametersCreateServiceCertificateServiceCertificateCreateParameters0 = catparametersCreateServiceCertificateServiceCertificateCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of service-certificate in the parameter file.')); - var setparametersCreateServiceCertificateServiceCertificateCreateParameters0 = parametersCreateServiceCertificateServiceCertificateCreateParameters0.category('set') + var setparametersCreateServiceCertificateServiceCertificateCreateParameters0 = parametersCreateServiceCertificateServiceCertificateCreateParameters0.category('service-certificate-create-parameters') .description($('Commands to set components of service-certificate in create-parameters file.')); - setparametersCreateServiceCertificateServiceCertificateCreateParameters0.command('service-certificate-create-parameters') + setparametersCreateServiceCertificateServiceCertificateCreateParameters0.command('set') .description($('Set service-certificate-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "certificateFormat":0,\r\n "data":null,\r\n "password":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15610,9 +15610,9 @@ exports.init = function (cli) { var catparametersCreateServiceCertificateServiceCertificateCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('service-certificate'); var parametersCreateServiceCertificateServiceCertificateCreateParameters1 = catparametersCreateServiceCertificateServiceCertificateCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of service-certificate in the parameter file.')); - var removeparametersCreateServiceCertificateServiceCertificateCreateParameters1 = parametersCreateServiceCertificateServiceCertificateCreateParameters1.category('remove') + var removeparametersCreateServiceCertificateServiceCertificateCreateParameters1 = parametersCreateServiceCertificateServiceCertificateCreateParameters1.category('service-certificate-create-parameters') .description($('Commands to remove components of service-certificate in create-parameters file.')); - removeparametersCreateServiceCertificateServiceCertificateCreateParameters1.command('service-certificate-create-parameters') + removeparametersCreateServiceCertificateServiceCertificateCreateParameters1.command('remove') .description($('Remove service-certificate-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "certificateFormat":0,\r\n "data":null,\r\n "password":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15664,9 +15664,9 @@ exports.init = function (cli) { var catparametersCreateServiceCertificateServiceCertificateCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('service-certificate'); var parametersCreateServiceCertificateServiceCertificateCreateParameters2 = catparametersCreateServiceCertificateServiceCertificateCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of service-certificate in the parameter file.')); - var addparametersCreateServiceCertificateServiceCertificateCreateParameters2 = parametersCreateServiceCertificateServiceCertificateCreateParameters2.category('add') + var addparametersCreateServiceCertificateServiceCertificateCreateParameters2 = parametersCreateServiceCertificateServiceCertificateCreateParameters2.category('service-certificate-create-parameters') .description($('Commands to add components of service-certificate in create-parameters file.')); - addparametersCreateServiceCertificateServiceCertificateCreateParameters2.command('service-certificate-create-parameters') + addparametersCreateServiceCertificateServiceCertificateCreateParameters2.command('add') .description($('Add service-certificate-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "certificateFormat":0,\r\n "data":null,\r\n "password":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15738,9 +15738,9 @@ exports.init = function (cli) { var catparametersCreateServiceCertificateCertificateFormat1 = cli.category('invoke').description('Commands to invoke service management operations.').category('service-certificate'); var parametersCreateServiceCertificateCertificateFormat1 = catparametersCreateServiceCertificateCertificateFormat1.category('create-parameters') .description($('Commands to manage configuration of service-certificate in the parameter file.')); - var removeparametersCreateServiceCertificateCertificateFormat1 = parametersCreateServiceCertificateCertificateFormat1.category('remove') + var removeparametersCreateServiceCertificateCertificateFormat1 = parametersCreateServiceCertificateCertificateFormat1.category('certificate-format') .description($('Commands to remove components of service-certificate in create-parameters file.')); - removeparametersCreateServiceCertificateCertificateFormat1.command('certificate-format') + removeparametersCreateServiceCertificateCertificateFormat1.command('remove') .description($('Remove certificate-format in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificateFormat" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -15770,9 +15770,9 @@ exports.init = function (cli) { var catparametersCreateServiceCertificateCertificateFormat2 = cli.category('invoke').description('Commands to invoke service management operations.').category('service-certificate'); var parametersCreateServiceCertificateCertificateFormat2 = catparametersCreateServiceCertificateCertificateFormat2.category('create-parameters') .description($('Commands to manage configuration of service-certificate in the parameter file.')); - var addparametersCreateServiceCertificateCertificateFormat2 = parametersCreateServiceCertificateCertificateFormat2.category('add') + var addparametersCreateServiceCertificateCertificateFormat2 = parametersCreateServiceCertificateCertificateFormat2.category('certificate-format') .description($('Commands to add components of service-certificate in create-parameters file.')); - addparametersCreateServiceCertificateCertificateFormat2.command('certificate-format') + addparametersCreateServiceCertificateCertificateFormat2.command('add') .description($('Add certificate-format in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "certificateFormat" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16050,9 +16050,9 @@ exports.init = function (cli) { var catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0 = catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0.category('create-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var setparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0.category('set') + var setparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0.category('virtual-machine-data-disk-create-parameters') .description($('Commands to set components of virtual-machine-disk in create-data-disk-parameters file.')); - setparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0.command('virtual-machine-data-disk-create-parameters') + setparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters0.command('set') .description($('Set virtual-machine-data-disk-create-parameters in create-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "sourceMediaLinkUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16164,9 +16164,9 @@ exports.init = function (cli) { var catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1 = catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1.category('create-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var removeparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1.category('remove') + var removeparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1.category('virtual-machine-data-disk-create-parameters') .description($('Commands to remove components of virtual-machine-disk in create-data-disk-parameters file.')); - removeparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1.command('virtual-machine-data-disk-create-parameters') + removeparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters1.command('remove') .description($('Remove virtual-machine-data-disk-create-parameters in create-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "sourceMediaLinkUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16238,9 +16238,9 @@ exports.init = function (cli) { var catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2 = catparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2.category('create-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var addparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2.category('add') + var addparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2 = parametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2.category('virtual-machine-data-disk-create-parameters') .description($('Commands to add components of virtual-machine-disk in create-data-disk-parameters file.')); - addparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2.command('virtual-machine-data-disk-create-parameters') + addparametersCreateDataDiskVirtualMachineDiskVirtualMachineDataDiskCreateParameters2.command('add') .description($('Add virtual-machine-data-disk-create-parameters in create-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "sourceMediaLinkUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16458,9 +16458,9 @@ exports.init = function (cli) { var catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0 = catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0.category('create-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var setparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0.category('set') + var setparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0.category('virtual-machine-disk-create-parameters') .description($('Commands to set components of virtual-machine-disk in create-disk-parameters file.')); - setparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0.command('virtual-machine-disk-create-parameters') + setparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters0.command('set') .description($('Set virtual-machine-disk-create-parameters in create-disk-parameters string or files, e.g. \r\n{\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16539,9 +16539,9 @@ exports.init = function (cli) { var catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1 = catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1.category('create-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var removeparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1.category('remove') + var removeparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1.category('virtual-machine-disk-create-parameters') .description($('Commands to remove components of virtual-machine-disk in create-disk-parameters file.')); - removeparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1.command('virtual-machine-disk-create-parameters') + removeparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters1.command('remove') .description($('Remove virtual-machine-disk-create-parameters in create-disk-parameters string or files, e.g. \r\n{\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -16598,9 +16598,9 @@ exports.init = function (cli) { var catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2 = catparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2.category('create-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var addparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2.category('add') + var addparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2 = parametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2.category('virtual-machine-disk-create-parameters') .description($('Commands to add components of virtual-machine-disk in create-disk-parameters file.')); - addparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2.command('virtual-machine-disk-create-parameters') + addparametersCreateDiskVirtualMachineDiskVirtualMachineDiskCreateParameters2.command('add') .description($('Add virtual-machine-disk-create-parameters in create-disk-parameters string or files, e.g. \r\n{\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17009,9 +17009,9 @@ exports.init = function (cli) { var catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0 = catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0.category('update-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var setparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0.category('set') + var setparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0.category('virtual-machine-data-disk-update-parameters') .description($('Commands to set components of virtual-machine-disk in update-data-disk-parameters file.')); - setparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0.command('virtual-machine-data-disk-update-parameters') + setparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters0.command('set') .description($('Set virtual-machine-data-disk-update-parameters in update-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17112,9 +17112,9 @@ exports.init = function (cli) { var catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1 = catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1.category('update-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var removeparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1.category('remove') + var removeparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1.category('virtual-machine-data-disk-update-parameters') .description($('Commands to remove components of virtual-machine-disk in update-data-disk-parameters file.')); - removeparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1.command('virtual-machine-data-disk-update-parameters') + removeparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters1.command('remove') .description($('Remove virtual-machine-data-disk-update-parameters in update-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17181,9 +17181,9 @@ exports.init = function (cli) { var catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2 = catparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2.category('update-data-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var addparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2.category('add') + var addparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2 = parametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2.category('virtual-machine-data-disk-update-parameters') .description($('Commands to add components of virtual-machine-disk in update-data-disk-parameters file.')); - addparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2.command('virtual-machine-data-disk-update-parameters') + addparametersUpdateDataDiskVirtualMachineDiskVirtualMachineDataDiskUpdateParameters2.command('add') .description($('Add virtual-machine-data-disk-update-parameters in update-data-disk-parameters string or files, e.g. \r\n{\r\n "hostCaching":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":0,\r\n "logicalUnitNumber":null,\r\n "mediaLinkUri":"",\r\n "name":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17399,9 +17399,9 @@ exports.init = function (cli) { var catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('update-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var setparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('set') + var setparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('virtual-machine-disk-update-parameters') .description($('Commands to set components of virtual-machine-disk in update-disk-parameters file.')); - setparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0.command('virtual-machine-disk-update-parameters') + setparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters0.command('set') .description($('Set virtual-machine-disk-update-parameters in update-disk-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17503,9 +17503,9 @@ exports.init = function (cli) { var catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('update-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var removeparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('remove') + var removeparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('virtual-machine-disk-update-parameters') .description($('Commands to remove components of virtual-machine-disk in update-disk-parameters file.')); - removeparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1.command('virtual-machine-disk-update-parameters') + removeparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters1.command('remove') .description($('Remove virtual-machine-disk-update-parameters in update-disk-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17572,9 +17572,9 @@ exports.init = function (cli) { var catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = catparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('update-disk-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var addparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('add') + var addparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = parametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('virtual-machine-disk-update-parameters') .description($('Commands to add components of virtual-machine-disk in update-disk-parameters file.')); - addparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2.command('virtual-machine-disk-update-parameters') + addparametersUpdateDiskVirtualMachineDiskVirtualMachineDiskUpdateParameters2.command('add') .description($('Add virtual-machine-disk-update-parameters in update-disk-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17791,9 +17791,9 @@ exports.init = function (cli) { var catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('update-disk-size-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var setparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('set') + var setparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0.category('virtual-machine-disk-update-parameters') .description($('Commands to set components of virtual-machine-disk in update-disk-size-parameters file.')); - setparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0.command('virtual-machine-disk-update-parameters') + setparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters0.command('set') .description($('Set virtual-machine-disk-update-parameters in update-disk-size-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17895,9 +17895,9 @@ exports.init = function (cli) { var catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('update-disk-size-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var removeparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('remove') + var removeparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1.category('virtual-machine-disk-update-parameters') .description($('Commands to remove components of virtual-machine-disk in update-disk-size-parameters file.')); - removeparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1.command('virtual-machine-disk-update-parameters') + removeparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters1.command('remove') .description($('Remove virtual-machine-disk-update-parameters in update-disk-size-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -17964,9 +17964,9 @@ exports.init = function (cli) { var catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-disk'); var parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = catparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('update-disk-size-parameters') .description($('Commands to manage configuration of virtual-machine-disk in the parameter file.')); - var addparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('add') + var addparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2 = parametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2.category('virtual-machine-disk-update-parameters') .description($('Commands to add components of virtual-machine-disk in update-disk-size-parameters file.')); - addparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2.command('virtual-machine-disk-update-parameters') + addparametersUpdateDiskSizeVirtualMachineDiskVirtualMachineDiskUpdateParameters2.command('add') .description($('Add virtual-machine-disk-update-parameters in update-disk-size-parameters string or files, e.g. \r\n{\r\n "hasOperatingSystem":null,\r\n "label":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "resizedSizeInGB":null\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18374,9 +18374,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0 = catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0.category('set') + var setparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0.category('virtual-machine-capture-os-image-parameters') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0.command('virtual-machine-capture-os-image-parameters') + setparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters0.command('set') .description($('Set virtual-machine-capture-os-image-parameters in capture-os-image-parameters string or files, e.g. \r\n{\r\n "postCaptureAction":0,\r\n "provisioningConfiguration":{\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n },\r\n "targetImageLabel":"",\r\n "targetImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18455,9 +18455,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1 = catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1.category('remove') + var removeparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1.category('virtual-machine-capture-os-image-parameters') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1.command('virtual-machine-capture-os-image-parameters') + removeparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters1.command('remove') .description($('Remove virtual-machine-capture-os-image-parameters in capture-os-image-parameters string or files, e.g. \r\n{\r\n "postCaptureAction":0,\r\n "provisioningConfiguration":{\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n },\r\n "targetImageLabel":"",\r\n "targetImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18514,9 +18514,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2 = catparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2.category('add') + var addparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2 = parametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2.category('virtual-machine-capture-os-image-parameters') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2.command('virtual-machine-capture-os-image-parameters') + addparametersCaptureOSImageVirtualMachineVirtualMachineCaptureOSImageParameters2.command('add') .description($('Add virtual-machine-capture-os-image-parameters in capture-os-image-parameters string or files, e.g. \r\n{\r\n "postCaptureAction":0,\r\n "provisioningConfiguration":{\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n },\r\n "targetImageLabel":"",\r\n "targetImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18599,9 +18599,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePostCaptureAction1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePostCaptureAction1 = catparametersCaptureOSImageVirtualMachinePostCaptureAction1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachinePostCaptureAction1 = parametersCaptureOSImageVirtualMachinePostCaptureAction1.category('remove') + var removeparametersCaptureOSImageVirtualMachinePostCaptureAction1 = parametersCaptureOSImageVirtualMachinePostCaptureAction1.category('post-capture-action') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachinePostCaptureAction1.command('post-capture-action') + removeparametersCaptureOSImageVirtualMachinePostCaptureAction1.command('remove') .description($('Remove post-capture-action in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "postCaptureAction" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18631,9 +18631,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePostCaptureAction2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePostCaptureAction2 = catparametersCaptureOSImageVirtualMachinePostCaptureAction2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachinePostCaptureAction2 = parametersCaptureOSImageVirtualMachinePostCaptureAction2.category('add') + var addparametersCaptureOSImageVirtualMachinePostCaptureAction2 = parametersCaptureOSImageVirtualMachinePostCaptureAction2.category('post-capture-action') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachinePostCaptureAction2.command('post-capture-action') + addparametersCaptureOSImageVirtualMachinePostCaptureAction2.command('add') .description($('Add post-capture-action in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "postCaptureAction" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18672,9 +18672,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioningConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioningConfiguration0 = catparametersCaptureOSImageVirtualMachineProvisioningConfiguration0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineProvisioningConfiguration0 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration0.category('set') + var setparametersCaptureOSImageVirtualMachineProvisioningConfiguration0 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration0.category('provisioning-configuration') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineProvisioningConfiguration0.command('provisioning-configuration') + setparametersCaptureOSImageVirtualMachineProvisioningConfiguration0.command('set') .description($('Set provisioning-configuration in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioningConfiguration" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -18976,9 +18976,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioningConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioningConfiguration1 = catparametersCaptureOSImageVirtualMachineProvisioningConfiguration1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineProvisioningConfiguration1 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration1.category('remove') + var removeparametersCaptureOSImageVirtualMachineProvisioningConfiguration1 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration1.category('provisioning-configuration') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineProvisioningConfiguration1.command('provisioning-configuration') + removeparametersCaptureOSImageVirtualMachineProvisioningConfiguration1.command('remove') .description($('Remove provisioning-configuration in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioningConfiguration" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19135,9 +19135,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioningConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioningConfiguration2 = catparametersCaptureOSImageVirtualMachineProvisioningConfiguration2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineProvisioningConfiguration2 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration2.category('add') + var addparametersCaptureOSImageVirtualMachineProvisioningConfiguration2 = parametersCaptureOSImageVirtualMachineProvisioningConfiguration2.category('provisioning-configuration') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineProvisioningConfiguration2.command('provisioning-configuration') + addparametersCaptureOSImageVirtualMachineProvisioningConfiguration2.command('add') .description($('Add provisioning-configuration in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioningConfiguration" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19443,9 +19443,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineAdditionalUnattendContent1 = catparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1 = parametersCaptureOSImageVirtualMachineAdditionalUnattendContent1.category('remove') + var removeparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1 = parametersCaptureOSImageVirtualMachineAdditionalUnattendContent1.category('additional-unattend-content') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1.command('additional-unattend-content') + removeparametersCaptureOSImageVirtualMachineAdditionalUnattendContent1.command('remove') .description($('Remove additional-unattend-content in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19487,9 +19487,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineAdditionalUnattendContent2 = catparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2 = parametersCaptureOSImageVirtualMachineAdditionalUnattendContent2.category('add') + var addparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2 = parametersCaptureOSImageVirtualMachineAdditionalUnattendContent2.category('additional-unattend-content') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2.command('additional-unattend-content') + addparametersCaptureOSImageVirtualMachineAdditionalUnattendContent2.command('add') .description($('Add additional-unattend-content in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19539,9 +19539,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendPasses0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendPasses0 = catparametersCaptureOSImageVirtualMachineUnattendPasses0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineUnattendPasses0 = parametersCaptureOSImageVirtualMachineUnattendPasses0.category('set') + var setparametersCaptureOSImageVirtualMachineUnattendPasses0 = parametersCaptureOSImageVirtualMachineUnattendPasses0.category('unattend-passes') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineUnattendPasses0.command('unattend-passes') + setparametersCaptureOSImageVirtualMachineUnattendPasses0.command('set') .description($('Set unattend-passes in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19603,9 +19603,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendPasses1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendPasses1 = catparametersCaptureOSImageVirtualMachineUnattendPasses1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineUnattendPasses1 = parametersCaptureOSImageVirtualMachineUnattendPasses1.category('remove') + var removeparametersCaptureOSImageVirtualMachineUnattendPasses1 = parametersCaptureOSImageVirtualMachineUnattendPasses1.category('unattend-passes') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineUnattendPasses1.command('unattend-passes') + removeparametersCaptureOSImageVirtualMachineUnattendPasses1.command('remove') .description($('Remove unattend-passes in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19653,9 +19653,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendPasses2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendPasses2 = catparametersCaptureOSImageVirtualMachineUnattendPasses2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineUnattendPasses2 = parametersCaptureOSImageVirtualMachineUnattendPasses2.category('add') + var addparametersCaptureOSImageVirtualMachineUnattendPasses2 = parametersCaptureOSImageVirtualMachineUnattendPasses2.category('unattend-passes') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineUnattendPasses2.command('unattend-passes') + addparametersCaptureOSImageVirtualMachineUnattendPasses2.command('add') .description($('Add unattend-passes in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19716,9 +19716,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponents0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponents0 = catparametersCaptureOSImageVirtualMachineUnattendComponents0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineUnattendComponents0 = parametersCaptureOSImageVirtualMachineUnattendComponents0.category('set') + var setparametersCaptureOSImageVirtualMachineUnattendComponents0 = parametersCaptureOSImageVirtualMachineUnattendComponents0.category('unattend-components') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineUnattendComponents0.command('unattend-components') + setparametersCaptureOSImageVirtualMachineUnattendComponents0.command('set') .description($('Set unattend-components in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19781,9 +19781,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponents1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponents1 = catparametersCaptureOSImageVirtualMachineUnattendComponents1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineUnattendComponents1 = parametersCaptureOSImageVirtualMachineUnattendComponents1.category('remove') + var removeparametersCaptureOSImageVirtualMachineUnattendComponents1 = parametersCaptureOSImageVirtualMachineUnattendComponents1.category('unattend-components') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineUnattendComponents1.command('unattend-components') + removeparametersCaptureOSImageVirtualMachineUnattendComponents1.command('remove') .description($('Remove unattend-components in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19832,9 +19832,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponents2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponents2 = catparametersCaptureOSImageVirtualMachineUnattendComponents2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineUnattendComponents2 = parametersCaptureOSImageVirtualMachineUnattendComponents2.category('add') + var addparametersCaptureOSImageVirtualMachineUnattendComponents2 = parametersCaptureOSImageVirtualMachineUnattendComponents2.category('unattend-components') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineUnattendComponents2.command('unattend-components') + addparametersCaptureOSImageVirtualMachineUnattendComponents2.command('add') .description($('Add unattend-components in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19895,9 +19895,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponentSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponentSettings0 = catparametersCaptureOSImageVirtualMachineUnattendComponentSettings0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineUnattendComponentSettings0 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings0.category('set') + var setparametersCaptureOSImageVirtualMachineUnattendComponentSettings0 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings0.category('unattend-component-settings') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineUnattendComponentSettings0.command('unattend-component-settings') + setparametersCaptureOSImageVirtualMachineUnattendComponentSettings0.command('set') .description($('Set unattend-component-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -19961,9 +19961,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponentSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponentSettings1 = catparametersCaptureOSImageVirtualMachineUnattendComponentSettings1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineUnattendComponentSettings1 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings1.category('remove') + var removeparametersCaptureOSImageVirtualMachineUnattendComponentSettings1 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings1.category('unattend-component-settings') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineUnattendComponentSettings1.command('unattend-component-settings') + removeparametersCaptureOSImageVirtualMachineUnattendComponentSettings1.command('remove') .description($('Remove unattend-component-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20013,9 +20013,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineUnattendComponentSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineUnattendComponentSettings2 = catparametersCaptureOSImageVirtualMachineUnattendComponentSettings2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineUnattendComponentSettings2 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings2.category('add') + var addparametersCaptureOSImageVirtualMachineUnattendComponentSettings2 = parametersCaptureOSImageVirtualMachineUnattendComponentSettings2.category('unattend-component-settings') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineUnattendComponentSettings2.command('unattend-component-settings') + addparametersCaptureOSImageVirtualMachineUnattendComponentSettings2.command('add') .description($('Add unattend-component-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20076,9 +20076,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineDomainJoin0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineDomainJoin0 = catparametersCaptureOSImageVirtualMachineDomainJoin0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineDomainJoin0 = parametersCaptureOSImageVirtualMachineDomainJoin0.category('set') + var setparametersCaptureOSImageVirtualMachineDomainJoin0 = parametersCaptureOSImageVirtualMachineDomainJoin0.category('domain-join') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineDomainJoin0.command('domain-join') + setparametersCaptureOSImageVirtualMachineDomainJoin0.command('set') .description($('Set domain-join in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20157,9 +20157,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineDomainJoin1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineDomainJoin1 = catparametersCaptureOSImageVirtualMachineDomainJoin1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineDomainJoin1 = parametersCaptureOSImageVirtualMachineDomainJoin1.category('remove') + var removeparametersCaptureOSImageVirtualMachineDomainJoin1 = parametersCaptureOSImageVirtualMachineDomainJoin1.category('domain-join') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineDomainJoin1.command('domain-join') + removeparametersCaptureOSImageVirtualMachineDomainJoin1.command('remove') .description($('Remove domain-join in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20216,9 +20216,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineDomainJoin2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineDomainJoin2 = catparametersCaptureOSImageVirtualMachineDomainJoin2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineDomainJoin2 = parametersCaptureOSImageVirtualMachineDomainJoin2.category('add') + var addparametersCaptureOSImageVirtualMachineDomainJoin2 = parametersCaptureOSImageVirtualMachineDomainJoin2.category('domain-join') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineDomainJoin2.command('domain-join') + addparametersCaptureOSImageVirtualMachineDomainJoin2.command('add') .description($('Add domain-join in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20301,9 +20301,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineCredentials0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineCredentials0 = catparametersCaptureOSImageVirtualMachineCredentials0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineCredentials0 = parametersCaptureOSImageVirtualMachineCredentials0.category('set') + var setparametersCaptureOSImageVirtualMachineCredentials0 = parametersCaptureOSImageVirtualMachineCredentials0.category('credentials') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineCredentials0.command('credentials') + setparametersCaptureOSImageVirtualMachineCredentials0.command('set') .description($('Set credentials in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20371,9 +20371,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineCredentials1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineCredentials1 = catparametersCaptureOSImageVirtualMachineCredentials1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineCredentials1 = parametersCaptureOSImageVirtualMachineCredentials1.category('remove') + var removeparametersCaptureOSImageVirtualMachineCredentials1 = parametersCaptureOSImageVirtualMachineCredentials1.category('credentials') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineCredentials1.command('credentials') + removeparametersCaptureOSImageVirtualMachineCredentials1.command('remove') .description($('Remove credentials in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20425,9 +20425,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineCredentials2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineCredentials2 = catparametersCaptureOSImageVirtualMachineCredentials2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineCredentials2 = parametersCaptureOSImageVirtualMachineCredentials2.category('add') + var addparametersCaptureOSImageVirtualMachineCredentials2 = parametersCaptureOSImageVirtualMachineCredentials2.category('credentials') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineCredentials2.command('credentials') + addparametersCaptureOSImageVirtualMachineCredentials2.command('add') .description($('Add credentials in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20499,9 +20499,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioning0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioning0 = catparametersCaptureOSImageVirtualMachineProvisioning0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineProvisioning0 = parametersCaptureOSImageVirtualMachineProvisioning0.category('set') + var setparametersCaptureOSImageVirtualMachineProvisioning0 = parametersCaptureOSImageVirtualMachineProvisioning0.category('provisioning') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineProvisioning0.command('provisioning') + setparametersCaptureOSImageVirtualMachineProvisioning0.command('set') .description($('Set provisioning in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20547,9 +20547,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioning1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioning1 = catparametersCaptureOSImageVirtualMachineProvisioning1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineProvisioning1 = parametersCaptureOSImageVirtualMachineProvisioning1.category('remove') + var removeparametersCaptureOSImageVirtualMachineProvisioning1 = parametersCaptureOSImageVirtualMachineProvisioning1.category('provisioning') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineProvisioning1.command('provisioning') + removeparametersCaptureOSImageVirtualMachineProvisioning1.command('remove') .description($('Remove provisioning in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20591,9 +20591,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProvisioning2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProvisioning2 = catparametersCaptureOSImageVirtualMachineProvisioning2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineProvisioning2 = parametersCaptureOSImageVirtualMachineProvisioning2.category('add') + var addparametersCaptureOSImageVirtualMachineProvisioning2 = parametersCaptureOSImageVirtualMachineProvisioning2.category('provisioning') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineProvisioning2.command('provisioning') + addparametersCaptureOSImageVirtualMachineProvisioning2.command('add') .description($('Add provisioning in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20643,9 +20643,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineInputEndpoints0 = catparametersCaptureOSImageVirtualMachineInputEndpoints0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineInputEndpoints0 = parametersCaptureOSImageVirtualMachineInputEndpoints0.category('set') + var setparametersCaptureOSImageVirtualMachineInputEndpoints0 = parametersCaptureOSImageVirtualMachineInputEndpoints0.category('input-endpoints') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineInputEndpoints0.command('input-endpoints') + setparametersCaptureOSImageVirtualMachineInputEndpoints0.command('set') .description($('Set input-endpoints in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20829,9 +20829,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineInputEndpoints1 = catparametersCaptureOSImageVirtualMachineInputEndpoints1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineInputEndpoints1 = parametersCaptureOSImageVirtualMachineInputEndpoints1.category('remove') + var removeparametersCaptureOSImageVirtualMachineInputEndpoints1 = parametersCaptureOSImageVirtualMachineInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineInputEndpoints1.command('input-endpoints') + removeparametersCaptureOSImageVirtualMachineInputEndpoints1.command('remove') .description($('Remove input-endpoints in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -20934,9 +20934,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineInputEndpoints2 = catparametersCaptureOSImageVirtualMachineInputEndpoints2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineInputEndpoints2 = parametersCaptureOSImageVirtualMachineInputEndpoints2.category('add') + var addparametersCaptureOSImageVirtualMachineInputEndpoints2 = parametersCaptureOSImageVirtualMachineInputEndpoints2.category('input-endpoints') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineInputEndpoints2.command('input-endpoints') + addparametersCaptureOSImageVirtualMachineInputEndpoints2.command('add') .description($('Add input-endpoints in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21119,9 +21119,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineEndpointAcl1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineEndpointAcl1 = catparametersCaptureOSImageVirtualMachineEndpointAcl1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineEndpointAcl1 = parametersCaptureOSImageVirtualMachineEndpointAcl1.category('remove') + var removeparametersCaptureOSImageVirtualMachineEndpointAcl1 = parametersCaptureOSImageVirtualMachineEndpointAcl1.category('endpoint-acl') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineEndpointAcl1.command('endpoint-acl') + removeparametersCaptureOSImageVirtualMachineEndpointAcl1.command('remove') .description($('Remove endpoint-acl in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21164,9 +21164,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineEndpointAcl2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineEndpointAcl2 = catparametersCaptureOSImageVirtualMachineEndpointAcl2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineEndpointAcl2 = parametersCaptureOSImageVirtualMachineEndpointAcl2.category('add') + var addparametersCaptureOSImageVirtualMachineEndpointAcl2 = parametersCaptureOSImageVirtualMachineEndpointAcl2.category('endpoint-acl') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineEndpointAcl2.command('endpoint-acl') + addparametersCaptureOSImageVirtualMachineEndpointAcl2.command('add') .description($('Add endpoint-acl in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21216,9 +21216,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineRules0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineRules0 = catparametersCaptureOSImageVirtualMachineRules0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineRules0 = parametersCaptureOSImageVirtualMachineRules0.category('set') + var setparametersCaptureOSImageVirtualMachineRules0 = parametersCaptureOSImageVirtualMachineRules0.category('rules') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineRules0.command('rules') + setparametersCaptureOSImageVirtualMachineRules0.command('set') .description($('Set rules in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21303,9 +21303,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineRules1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineRules1 = catparametersCaptureOSImageVirtualMachineRules1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineRules1 = parametersCaptureOSImageVirtualMachineRules1.category('remove') + var removeparametersCaptureOSImageVirtualMachineRules1 = parametersCaptureOSImageVirtualMachineRules1.category('rules') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineRules1.command('rules') + removeparametersCaptureOSImageVirtualMachineRules1.command('remove') .description($('Remove rules in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21364,9 +21364,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineRules2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineRules2 = catparametersCaptureOSImageVirtualMachineRules2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineRules2 = parametersCaptureOSImageVirtualMachineRules2.category('add') + var addparametersCaptureOSImageVirtualMachineRules2 = parametersCaptureOSImageVirtualMachineRules2.category('rules') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineRules2.command('rules') + addparametersCaptureOSImageVirtualMachineRules2.command('add') .description($('Add rules in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21449,9 +21449,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineLoadBalancerProbe0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineLoadBalancerProbe0 = catparametersCaptureOSImageVirtualMachineLoadBalancerProbe0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineLoadBalancerProbe0 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe0.category('set') + var setparametersCaptureOSImageVirtualMachineLoadBalancerProbe0 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe0.category('load-balancer-probe') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineLoadBalancerProbe0.command('load-balancer-probe') + setparametersCaptureOSImageVirtualMachineLoadBalancerProbe0.command('set') .description($('Set load-balancer-probe in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21542,9 +21542,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineLoadBalancerProbe1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineLoadBalancerProbe1 = catparametersCaptureOSImageVirtualMachineLoadBalancerProbe1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineLoadBalancerProbe1 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe1.category('remove') + var removeparametersCaptureOSImageVirtualMachineLoadBalancerProbe1 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe1.category('load-balancer-probe') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineLoadBalancerProbe1.command('load-balancer-probe') + removeparametersCaptureOSImageVirtualMachineLoadBalancerProbe1.command('remove') .description($('Remove load-balancer-probe in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21607,9 +21607,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineLoadBalancerProbe2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineLoadBalancerProbe2 = catparametersCaptureOSImageVirtualMachineLoadBalancerProbe2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineLoadBalancerProbe2 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe2.category('add') + var addparametersCaptureOSImageVirtualMachineLoadBalancerProbe2 = parametersCaptureOSImageVirtualMachineLoadBalancerProbe2.category('load-balancer-probe') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineLoadBalancerProbe2.command('load-balancer-probe') + addparametersCaptureOSImageVirtualMachineLoadBalancerProbe2.command('add') .description($('Add load-balancer-probe in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21703,9 +21703,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProtocol1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProtocol1 = catparametersCaptureOSImageVirtualMachineProtocol1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineProtocol1 = parametersCaptureOSImageVirtualMachineProtocol1.category('remove') + var removeparametersCaptureOSImageVirtualMachineProtocol1 = parametersCaptureOSImageVirtualMachineProtocol1.category('protocol') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineProtocol1.command('protocol') + removeparametersCaptureOSImageVirtualMachineProtocol1.command('remove') .description($('Remove protocol in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21737,9 +21737,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineProtocol2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineProtocol2 = catparametersCaptureOSImageVirtualMachineProtocol2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineProtocol2 = parametersCaptureOSImageVirtualMachineProtocol2.category('add') + var addparametersCaptureOSImageVirtualMachineProtocol2 = parametersCaptureOSImageVirtualMachineProtocol2.category('protocol') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineProtocol2.command('protocol') + addparametersCaptureOSImageVirtualMachineProtocol2.command('add') .description($('Add protocol in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21778,9 +21778,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineNetworkInterfaces0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineNetworkInterfaces0 = catparametersCaptureOSImageVirtualMachineNetworkInterfaces0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineNetworkInterfaces0 = parametersCaptureOSImageVirtualMachineNetworkInterfaces0.category('set') + var setparametersCaptureOSImageVirtualMachineNetworkInterfaces0 = parametersCaptureOSImageVirtualMachineNetworkInterfaces0.category('network-interfaces') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineNetworkInterfaces0.command('network-interfaces') + setparametersCaptureOSImageVirtualMachineNetworkInterfaces0.command('set') .description($('Set network-interfaces in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21864,9 +21864,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineNetworkInterfaces1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineNetworkInterfaces1 = catparametersCaptureOSImageVirtualMachineNetworkInterfaces1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineNetworkInterfaces1 = parametersCaptureOSImageVirtualMachineNetworkInterfaces1.category('remove') + var removeparametersCaptureOSImageVirtualMachineNetworkInterfaces1 = parametersCaptureOSImageVirtualMachineNetworkInterfaces1.category('network-interfaces') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineNetworkInterfaces1.command('network-interfaces') + removeparametersCaptureOSImageVirtualMachineNetworkInterfaces1.command('remove') .description($('Remove network-interfaces in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -21924,9 +21924,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineNetworkInterfaces2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineNetworkInterfaces2 = catparametersCaptureOSImageVirtualMachineNetworkInterfaces2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineNetworkInterfaces2 = parametersCaptureOSImageVirtualMachineNetworkInterfaces2.category('add') + var addparametersCaptureOSImageVirtualMachineNetworkInterfaces2 = parametersCaptureOSImageVirtualMachineNetworkInterfaces2.category('network-interfaces') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineNetworkInterfaces2.command('network-interfaces') + addparametersCaptureOSImageVirtualMachineNetworkInterfaces2.command('add') .description($('Add network-interfaces in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22009,9 +22009,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineIPConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineIPConfigurations0 = catparametersCaptureOSImageVirtualMachineIPConfigurations0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineIPConfigurations0 = parametersCaptureOSImageVirtualMachineIPConfigurations0.category('set') + var setparametersCaptureOSImageVirtualMachineIPConfigurations0 = parametersCaptureOSImageVirtualMachineIPConfigurations0.category('ip-configurations') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineIPConfigurations0.command('ip-configurations') + setparametersCaptureOSImageVirtualMachineIPConfigurations0.command('set') .description($('Set ip-configurations in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22074,9 +22074,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineIPConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineIPConfigurations1 = catparametersCaptureOSImageVirtualMachineIPConfigurations1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineIPConfigurations1 = parametersCaptureOSImageVirtualMachineIPConfigurations1.category('remove') + var removeparametersCaptureOSImageVirtualMachineIPConfigurations1 = parametersCaptureOSImageVirtualMachineIPConfigurations1.category('ip-configurations') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineIPConfigurations1.command('ip-configurations') + removeparametersCaptureOSImageVirtualMachineIPConfigurations1.command('remove') .description($('Remove ip-configurations in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22125,9 +22125,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineIPConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineIPConfigurations2 = catparametersCaptureOSImageVirtualMachineIPConfigurations2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineIPConfigurations2 = parametersCaptureOSImageVirtualMachineIPConfigurations2.category('add') + var addparametersCaptureOSImageVirtualMachineIPConfigurations2 = parametersCaptureOSImageVirtualMachineIPConfigurations2.category('ip-configurations') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineIPConfigurations2.command('ip-configurations') + addparametersCaptureOSImageVirtualMachineIPConfigurations2.command('add') .description($('Add ip-configurations in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22188,9 +22188,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicIPs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicIPs0 = catparametersCaptureOSImageVirtualMachinePublicIPs0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachinePublicIPs0 = parametersCaptureOSImageVirtualMachinePublicIPs0.category('set') + var setparametersCaptureOSImageVirtualMachinePublicIPs0 = parametersCaptureOSImageVirtualMachinePublicIPs0.category('public-ip') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachinePublicIPs0.command('public-ip') + setparametersCaptureOSImageVirtualMachinePublicIPs0.command('set') .description($('Set public-ip in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22263,9 +22263,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicIPs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicIPs1 = catparametersCaptureOSImageVirtualMachinePublicIPs1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachinePublicIPs1 = parametersCaptureOSImageVirtualMachinePublicIPs1.category('remove') + var removeparametersCaptureOSImageVirtualMachinePublicIPs1 = parametersCaptureOSImageVirtualMachinePublicIPs1.category('public-ip') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachinePublicIPs1.command('public-ip') + removeparametersCaptureOSImageVirtualMachinePublicIPs1.command('remove') .description($('Remove public-ip in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22318,9 +22318,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicIPs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicIPs2 = catparametersCaptureOSImageVirtualMachinePublicIPs2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachinePublicIPs2 = parametersCaptureOSImageVirtualMachinePublicIPs2.category('add') + var addparametersCaptureOSImageVirtualMachinePublicIPs2 = parametersCaptureOSImageVirtualMachinePublicIPs2.category('public-ip') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachinePublicIPs2.command('public-ip') + addparametersCaptureOSImageVirtualMachinePublicIPs2.command('add') .description($('Add public-ip in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22392,9 +22392,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineSshSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineSshSettings1 = catparametersCaptureOSImageVirtualMachineSshSettings1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineSshSettings1 = parametersCaptureOSImageVirtualMachineSshSettings1.category('remove') + var removeparametersCaptureOSImageVirtualMachineSshSettings1 = parametersCaptureOSImageVirtualMachineSshSettings1.category('ssh-settings') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineSshSettings1.command('ssh-settings') + removeparametersCaptureOSImageVirtualMachineSshSettings1.command('remove') .description($('Remove ssh-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22441,9 +22441,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineSshSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineSshSettings2 = catparametersCaptureOSImageVirtualMachineSshSettings2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineSshSettings2 = parametersCaptureOSImageVirtualMachineSshSettings2.category('add') + var addparametersCaptureOSImageVirtualMachineSshSettings2 = parametersCaptureOSImageVirtualMachineSshSettings2.category('ssh-settings') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineSshSettings2.command('ssh-settings') + addparametersCaptureOSImageVirtualMachineSshSettings2.command('add') .description($('Add ssh-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22504,9 +22504,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineKeyPairs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineKeyPairs0 = catparametersCaptureOSImageVirtualMachineKeyPairs0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineKeyPairs0 = parametersCaptureOSImageVirtualMachineKeyPairs0.category('set') + var setparametersCaptureOSImageVirtualMachineKeyPairs0 = parametersCaptureOSImageVirtualMachineKeyPairs0.category('key-pairs') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineKeyPairs0.command('key-pairs') + setparametersCaptureOSImageVirtualMachineKeyPairs0.command('set') .description($('Set key-pairs in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22568,9 +22568,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineKeyPairs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineKeyPairs1 = catparametersCaptureOSImageVirtualMachineKeyPairs1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineKeyPairs1 = parametersCaptureOSImageVirtualMachineKeyPairs1.category('remove') + var removeparametersCaptureOSImageVirtualMachineKeyPairs1 = parametersCaptureOSImageVirtualMachineKeyPairs1.category('key-pairs') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineKeyPairs1.command('key-pairs') + removeparametersCaptureOSImageVirtualMachineKeyPairs1.command('remove') .description($('Remove key-pairs in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22618,9 +22618,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineKeyPairs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineKeyPairs2 = catparametersCaptureOSImageVirtualMachineKeyPairs2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineKeyPairs2 = parametersCaptureOSImageVirtualMachineKeyPairs2.category('add') + var addparametersCaptureOSImageVirtualMachineKeyPairs2 = parametersCaptureOSImageVirtualMachineKeyPairs2.category('key-pairs') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineKeyPairs2.command('key-pairs') + addparametersCaptureOSImageVirtualMachineKeyPairs2.command('add') .description($('Add key-pairs in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22681,9 +22681,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicKeys0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicKeys0 = catparametersCaptureOSImageVirtualMachinePublicKeys0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachinePublicKeys0 = parametersCaptureOSImageVirtualMachinePublicKeys0.category('set') + var setparametersCaptureOSImageVirtualMachinePublicKeys0 = parametersCaptureOSImageVirtualMachinePublicKeys0.category('public-keys') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachinePublicKeys0.command('public-keys') + setparametersCaptureOSImageVirtualMachinePublicKeys0.command('set') .description($('Set public-keys in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22745,9 +22745,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicKeys1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicKeys1 = catparametersCaptureOSImageVirtualMachinePublicKeys1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachinePublicKeys1 = parametersCaptureOSImageVirtualMachinePublicKeys1.category('remove') + var removeparametersCaptureOSImageVirtualMachinePublicKeys1 = parametersCaptureOSImageVirtualMachinePublicKeys1.category('public-keys') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachinePublicKeys1.command('public-keys') + removeparametersCaptureOSImageVirtualMachinePublicKeys1.command('remove') .description($('Remove public-keys in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22795,9 +22795,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachinePublicKeys2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachinePublicKeys2 = catparametersCaptureOSImageVirtualMachinePublicKeys2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachinePublicKeys2 = parametersCaptureOSImageVirtualMachinePublicKeys2.category('add') + var addparametersCaptureOSImageVirtualMachinePublicKeys2 = parametersCaptureOSImageVirtualMachinePublicKeys2.category('public-keys') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachinePublicKeys2.command('public-keys') + addparametersCaptureOSImageVirtualMachinePublicKeys2.command('add') .description($('Add public-keys in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22858,9 +22858,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineStoredCertificateSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineStoredCertificateSettings0 = catparametersCaptureOSImageVirtualMachineStoredCertificateSettings0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineStoredCertificateSettings0 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings0.category('set') + var setparametersCaptureOSImageVirtualMachineStoredCertificateSettings0 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings0.category('stored-certificate-settings') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineStoredCertificateSettings0.command('stored-certificate-settings') + setparametersCaptureOSImageVirtualMachineStoredCertificateSettings0.command('set') .description($('Set stored-certificate-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22922,9 +22922,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineStoredCertificateSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineStoredCertificateSettings1 = catparametersCaptureOSImageVirtualMachineStoredCertificateSettings1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineStoredCertificateSettings1 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings1.category('remove') + var removeparametersCaptureOSImageVirtualMachineStoredCertificateSettings1 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings1.category('stored-certificate-settings') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineStoredCertificateSettings1.command('stored-certificate-settings') + removeparametersCaptureOSImageVirtualMachineStoredCertificateSettings1.command('remove') .description($('Remove stored-certificate-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -22972,9 +22972,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineStoredCertificateSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineStoredCertificateSettings2 = catparametersCaptureOSImageVirtualMachineStoredCertificateSettings2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineStoredCertificateSettings2 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings2.category('add') + var addparametersCaptureOSImageVirtualMachineStoredCertificateSettings2 = parametersCaptureOSImageVirtualMachineStoredCertificateSettings2.category('stored-certificate-settings') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineStoredCertificateSettings2.command('stored-certificate-settings') + addparametersCaptureOSImageVirtualMachineStoredCertificateSettings2.command('add') .description($('Add stored-certificate-settings in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23035,9 +23035,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineSubnetNames0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineSubnetNames0 = catparametersCaptureOSImageVirtualMachineSubnetNames0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineSubnetNames0 = parametersCaptureOSImageVirtualMachineSubnetNames0.category('set') + var setparametersCaptureOSImageVirtualMachineSubnetNames0 = parametersCaptureOSImageVirtualMachineSubnetNames0.category('subnet-names') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineSubnetNames0.command('subnet-names') + setparametersCaptureOSImageVirtualMachineSubnetNames0.command('set') .description($('Set subnet-names in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23077,9 +23077,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineSubnetNames1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineSubnetNames1 = catparametersCaptureOSImageVirtualMachineSubnetNames1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineSubnetNames1 = parametersCaptureOSImageVirtualMachineSubnetNames1.category('remove') + var removeparametersCaptureOSImageVirtualMachineSubnetNames1 = parametersCaptureOSImageVirtualMachineSubnetNames1.category('subnet-names') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineSubnetNames1.command('subnet-names') + removeparametersCaptureOSImageVirtualMachineSubnetNames1.command('remove') .description($('Remove subnet-names in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23111,9 +23111,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineSubnetNames2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineSubnetNames2 = catparametersCaptureOSImageVirtualMachineSubnetNames2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineSubnetNames2 = parametersCaptureOSImageVirtualMachineSubnetNames2.category('add') + var addparametersCaptureOSImageVirtualMachineSubnetNames2 = parametersCaptureOSImageVirtualMachineSubnetNames2.category('subnet-names') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineSubnetNames2.command('subnet-names') + addparametersCaptureOSImageVirtualMachineSubnetNames2.command('add') .description($('Add subnet-names in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23152,9 +23152,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineWindowsRemoteManagement1 = catparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1 = parametersCaptureOSImageVirtualMachineWindowsRemoteManagement1.category('remove') + var removeparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1 = parametersCaptureOSImageVirtualMachineWindowsRemoteManagement1.category('windows-remote-management') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1.command('windows-remote-management') + removeparametersCaptureOSImageVirtualMachineWindowsRemoteManagement1.command('remove') .description($('Remove windows-remote-management in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23196,9 +23196,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineWindowsRemoteManagement2 = catparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2 = parametersCaptureOSImageVirtualMachineWindowsRemoteManagement2.category('add') + var addparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2 = parametersCaptureOSImageVirtualMachineWindowsRemoteManagement2.category('windows-remote-management') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2.command('windows-remote-management') + addparametersCaptureOSImageVirtualMachineWindowsRemoteManagement2.command('add') .description($('Add windows-remote-management in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23248,9 +23248,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineListeners0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineListeners0 = catparametersCaptureOSImageVirtualMachineListeners0.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureOSImageVirtualMachineListeners0 = parametersCaptureOSImageVirtualMachineListeners0.category('set') + var setparametersCaptureOSImageVirtualMachineListeners0 = parametersCaptureOSImageVirtualMachineListeners0.category('listeners') .description($('Commands to set components of virtual-machine in capture-os-image-parameters file.')); - setparametersCaptureOSImageVirtualMachineListeners0.command('listeners') + setparametersCaptureOSImageVirtualMachineListeners0.command('set') .description($('Set listeners in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23312,9 +23312,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineListeners1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineListeners1 = catparametersCaptureOSImageVirtualMachineListeners1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineListeners1 = parametersCaptureOSImageVirtualMachineListeners1.category('remove') + var removeparametersCaptureOSImageVirtualMachineListeners1 = parametersCaptureOSImageVirtualMachineListeners1.category('listeners') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineListeners1.command('listeners') + removeparametersCaptureOSImageVirtualMachineListeners1.command('remove') .description($('Remove listeners in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23362,9 +23362,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineListeners2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineListeners2 = catparametersCaptureOSImageVirtualMachineListeners2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineListeners2 = parametersCaptureOSImageVirtualMachineListeners2.category('add') + var addparametersCaptureOSImageVirtualMachineListeners2 = parametersCaptureOSImageVirtualMachineListeners2.category('listeners') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineListeners2.command('listeners') + addparametersCaptureOSImageVirtualMachineListeners2.command('add') .description($('Add listeners in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23425,9 +23425,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineListenerType1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineListenerType1 = catparametersCaptureOSImageVirtualMachineListenerType1.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureOSImageVirtualMachineListenerType1 = parametersCaptureOSImageVirtualMachineListenerType1.category('remove') + var removeparametersCaptureOSImageVirtualMachineListenerType1 = parametersCaptureOSImageVirtualMachineListenerType1.category('listener-type') .description($('Commands to remove components of virtual-machine in capture-os-image-parameters file.')); - removeparametersCaptureOSImageVirtualMachineListenerType1.command('listener-type') + removeparametersCaptureOSImageVirtualMachineListenerType1.command('remove') .description($('Remove listener-type in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23459,9 +23459,9 @@ exports.init = function (cli) { var catparametersCaptureOSImageVirtualMachineListenerType2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureOSImageVirtualMachineListenerType2 = catparametersCaptureOSImageVirtualMachineListenerType2.category('capture-os-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureOSImageVirtualMachineListenerType2 = parametersCaptureOSImageVirtualMachineListenerType2.category('add') + var addparametersCaptureOSImageVirtualMachineListenerType2 = parametersCaptureOSImageVirtualMachineListenerType2.category('listener-type') .description($('Commands to add components of virtual-machine in capture-os-image-parameters file.')); - addparametersCaptureOSImageVirtualMachineListenerType2.command('listener-type') + addparametersCaptureOSImageVirtualMachineListenerType2.command('add') .description($('Add listener-type in capture-os-image-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23625,9 +23625,9 @@ exports.init = function (cli) { var catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0 = catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0.category('capture-vm-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0.category('set') + var setparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0.category('virtual-machine-capture-vm-image-parameters') .description($('Commands to set components of virtual-machine in capture-vm-image-parameters file.')); - setparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0.command('virtual-machine-capture-vm-image-parameters') + setparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters0.command('set') .description($('Set virtual-machine-capture-vm-image-parameters in capture-vm-image-parameters string or files, e.g. \r\n{\r\n "operationType":"",\r\n "oSState":"",\r\n "vMImageLabel":"",\r\n "vMImageName":"",\r\n "requestId":"",\r\n "statusCode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23728,9 +23728,9 @@ exports.init = function (cli) { var catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1 = catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1.category('capture-vm-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1.category('remove') + var removeparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1.category('virtual-machine-capture-vm-image-parameters') .description($('Commands to remove components of virtual-machine in capture-vm-image-parameters file.')); - removeparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1.command('virtual-machine-capture-vm-image-parameters') + removeparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters1.command('remove') .description($('Remove virtual-machine-capture-vm-image-parameters in capture-vm-image-parameters string or files, e.g. \r\n{\r\n "operationType":"",\r\n "oSState":"",\r\n "vMImageLabel":"",\r\n "vMImageName":"",\r\n "requestId":"",\r\n "statusCode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -23797,9 +23797,9 @@ exports.init = function (cli) { var catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2 = catparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2.category('capture-vm-image-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2.category('add') + var addparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2 = parametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2.category('virtual-machine-capture-vm-image-parameters') .description($('Commands to add components of virtual-machine in capture-vm-image-parameters file.')); - addparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2.command('virtual-machine-capture-vm-image-parameters') + addparametersCaptureVMImageVirtualMachineVirtualMachineCaptureVMImageParameters2.command('add') .description($('Add virtual-machine-capture-vm-image-parameters in capture-vm-image-parameters string or files, e.g. \r\n{\r\n "operationType":"",\r\n "oSState":"",\r\n "vMImageLabel":"",\r\n "vMImageName":"",\r\n "requestId":"",\r\n "statusCode":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -24210,9 +24210,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVirtualMachineCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineVirtualMachineCreateParameters0 = catparametersCreateVirtualMachineVirtualMachineCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineVirtualMachineCreateParameters0 = parametersCreateVirtualMachineVirtualMachineCreateParameters0.category('set') + var setparametersCreateVirtualMachineVirtualMachineCreateParameters0 = parametersCreateVirtualMachineVirtualMachineCreateParameters0.category('virtual-machine-create-parameters') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineVirtualMachineCreateParameters0.command('virtual-machine-create-parameters') + setparametersCreateVirtualMachineVirtualMachineCreateParameters0.command('set') .description($('Set virtual-machine-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "mediaLocation":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -24380,9 +24380,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVirtualMachineCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineVirtualMachineCreateParameters1 = catparametersCreateVirtualMachineVirtualMachineCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineVirtualMachineCreateParameters1 = parametersCreateVirtualMachineVirtualMachineCreateParameters1.category('remove') + var removeparametersCreateVirtualMachineVirtualMachineCreateParameters1 = parametersCreateVirtualMachineVirtualMachineCreateParameters1.category('virtual-machine-create-parameters') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineVirtualMachineCreateParameters1.command('virtual-machine-create-parameters') + removeparametersCreateVirtualMachineVirtualMachineCreateParameters1.command('remove') .description($('Remove virtual-machine-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "mediaLocation":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -24479,9 +24479,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVirtualMachineCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineVirtualMachineCreateParameters2 = catparametersCreateVirtualMachineVirtualMachineCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineVirtualMachineCreateParameters2 = parametersCreateVirtualMachineVirtualMachineCreateParameters2.category('add') + var addparametersCreateVirtualMachineVirtualMachineCreateParameters2 = parametersCreateVirtualMachineVirtualMachineCreateParameters2.category('virtual-machine-create-parameters') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineVirtualMachineCreateParameters2.command('virtual-machine-create-parameters') + addparametersCreateVirtualMachineVirtualMachineCreateParameters2.command('add') .description($('Add virtual-machine-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "mediaLocation":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -24653,9 +24653,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineConfigurationSets0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineConfigurationSets0 = catparametersCreateVirtualMachineConfigurationSets0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineConfigurationSets0 = parametersCreateVirtualMachineConfigurationSets0.category('set') + var setparametersCreateVirtualMachineConfigurationSets0 = parametersCreateVirtualMachineConfigurationSets0.category('configuration-sets') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineConfigurationSets0.command('configuration-sets') + setparametersCreateVirtualMachineConfigurationSets0.command('set') .description($('Set configuration-sets in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -24962,9 +24962,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineConfigurationSets1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineConfigurationSets1 = catparametersCreateVirtualMachineConfigurationSets1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineConfigurationSets1 = parametersCreateVirtualMachineConfigurationSets1.category('remove') + var removeparametersCreateVirtualMachineConfigurationSets1 = parametersCreateVirtualMachineConfigurationSets1.category('configuration-sets') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineConfigurationSets1.command('configuration-sets') + removeparametersCreateVirtualMachineConfigurationSets1.command('remove') .description($('Remove configuration-sets in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25122,9 +25122,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineConfigurationSets2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineConfigurationSets2 = catparametersCreateVirtualMachineConfigurationSets2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineConfigurationSets2 = parametersCreateVirtualMachineConfigurationSets2.category('add') + var addparametersCreateVirtualMachineConfigurationSets2 = parametersCreateVirtualMachineConfigurationSets2.category('configuration-sets') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineConfigurationSets2.command('configuration-sets') + addparametersCreateVirtualMachineConfigurationSets2.command('add') .description($('Add configuration-sets in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25430,9 +25430,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineAdditionalUnattendContent1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineAdditionalUnattendContent1 = catparametersCreateVirtualMachineAdditionalUnattendContent1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineAdditionalUnattendContent1 = parametersCreateVirtualMachineAdditionalUnattendContent1.category('remove') + var removeparametersCreateVirtualMachineAdditionalUnattendContent1 = parametersCreateVirtualMachineAdditionalUnattendContent1.category('additional-unattend-content') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineAdditionalUnattendContent1.command('additional-unattend-content') + removeparametersCreateVirtualMachineAdditionalUnattendContent1.command('remove') .description($('Remove additional-unattend-content in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25475,9 +25475,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineAdditionalUnattendContent2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineAdditionalUnattendContent2 = catparametersCreateVirtualMachineAdditionalUnattendContent2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineAdditionalUnattendContent2 = parametersCreateVirtualMachineAdditionalUnattendContent2.category('add') + var addparametersCreateVirtualMachineAdditionalUnattendContent2 = parametersCreateVirtualMachineAdditionalUnattendContent2.category('additional-unattend-content') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineAdditionalUnattendContent2.command('additional-unattend-content') + addparametersCreateVirtualMachineAdditionalUnattendContent2.command('add') .description($('Add additional-unattend-content in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25527,9 +25527,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendPasses0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendPasses0 = catparametersCreateVirtualMachineUnattendPasses0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineUnattendPasses0 = parametersCreateVirtualMachineUnattendPasses0.category('set') + var setparametersCreateVirtualMachineUnattendPasses0 = parametersCreateVirtualMachineUnattendPasses0.category('unattend-passes') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineUnattendPasses0.command('unattend-passes') + setparametersCreateVirtualMachineUnattendPasses0.command('set') .description($('Set unattend-passes in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25592,9 +25592,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendPasses1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendPasses1 = catparametersCreateVirtualMachineUnattendPasses1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineUnattendPasses1 = parametersCreateVirtualMachineUnattendPasses1.category('remove') + var removeparametersCreateVirtualMachineUnattendPasses1 = parametersCreateVirtualMachineUnattendPasses1.category('unattend-passes') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineUnattendPasses1.command('unattend-passes') + removeparametersCreateVirtualMachineUnattendPasses1.command('remove') .description($('Remove unattend-passes in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25643,9 +25643,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendPasses2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendPasses2 = catparametersCreateVirtualMachineUnattendPasses2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineUnattendPasses2 = parametersCreateVirtualMachineUnattendPasses2.category('add') + var addparametersCreateVirtualMachineUnattendPasses2 = parametersCreateVirtualMachineUnattendPasses2.category('unattend-passes') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineUnattendPasses2.command('unattend-passes') + addparametersCreateVirtualMachineUnattendPasses2.command('add') .description($('Add unattend-passes in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25706,9 +25706,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponents0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponents0 = catparametersCreateVirtualMachineUnattendComponents0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineUnattendComponents0 = parametersCreateVirtualMachineUnattendComponents0.category('set') + var setparametersCreateVirtualMachineUnattendComponents0 = parametersCreateVirtualMachineUnattendComponents0.category('unattend-components') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineUnattendComponents0.command('unattend-components') + setparametersCreateVirtualMachineUnattendComponents0.command('set') .description($('Set unattend-components in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25772,9 +25772,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponents1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponents1 = catparametersCreateVirtualMachineUnattendComponents1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineUnattendComponents1 = parametersCreateVirtualMachineUnattendComponents1.category('remove') + var removeparametersCreateVirtualMachineUnattendComponents1 = parametersCreateVirtualMachineUnattendComponents1.category('unattend-components') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineUnattendComponents1.command('unattend-components') + removeparametersCreateVirtualMachineUnattendComponents1.command('remove') .description($('Remove unattend-components in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25824,9 +25824,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponents2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponents2 = catparametersCreateVirtualMachineUnattendComponents2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineUnattendComponents2 = parametersCreateVirtualMachineUnattendComponents2.category('add') + var addparametersCreateVirtualMachineUnattendComponents2 = parametersCreateVirtualMachineUnattendComponents2.category('unattend-components') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineUnattendComponents2.command('unattend-components') + addparametersCreateVirtualMachineUnattendComponents2.command('add') .description($('Add unattend-components in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25887,9 +25887,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponentSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponentSettings0 = catparametersCreateVirtualMachineUnattendComponentSettings0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineUnattendComponentSettings0 = parametersCreateVirtualMachineUnattendComponentSettings0.category('set') + var setparametersCreateVirtualMachineUnattendComponentSettings0 = parametersCreateVirtualMachineUnattendComponentSettings0.category('unattend-component-settings') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineUnattendComponentSettings0.command('unattend-component-settings') + setparametersCreateVirtualMachineUnattendComponentSettings0.command('set') .description($('Set unattend-component-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -25954,9 +25954,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponentSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponentSettings1 = catparametersCreateVirtualMachineUnattendComponentSettings1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineUnattendComponentSettings1 = parametersCreateVirtualMachineUnattendComponentSettings1.category('remove') + var removeparametersCreateVirtualMachineUnattendComponentSettings1 = parametersCreateVirtualMachineUnattendComponentSettings1.category('unattend-component-settings') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineUnattendComponentSettings1.command('unattend-component-settings') + removeparametersCreateVirtualMachineUnattendComponentSettings1.command('remove') .description($('Remove unattend-component-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26007,9 +26007,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineUnattendComponentSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineUnattendComponentSettings2 = catparametersCreateVirtualMachineUnattendComponentSettings2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineUnattendComponentSettings2 = parametersCreateVirtualMachineUnattendComponentSettings2.category('add') + var addparametersCreateVirtualMachineUnattendComponentSettings2 = parametersCreateVirtualMachineUnattendComponentSettings2.category('unattend-component-settings') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineUnattendComponentSettings2.command('unattend-component-settings') + addparametersCreateVirtualMachineUnattendComponentSettings2.command('add') .description($('Add unattend-component-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26070,9 +26070,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDomainJoin0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDomainJoin0 = catparametersCreateVirtualMachineDomainJoin0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineDomainJoin0 = parametersCreateVirtualMachineDomainJoin0.category('set') + var setparametersCreateVirtualMachineDomainJoin0 = parametersCreateVirtualMachineDomainJoin0.category('domain-join') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineDomainJoin0.command('domain-join') + setparametersCreateVirtualMachineDomainJoin0.command('set') .description($('Set domain-join in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26152,9 +26152,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDomainJoin1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDomainJoin1 = catparametersCreateVirtualMachineDomainJoin1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineDomainJoin1 = parametersCreateVirtualMachineDomainJoin1.category('remove') + var removeparametersCreateVirtualMachineDomainJoin1 = parametersCreateVirtualMachineDomainJoin1.category('domain-join') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineDomainJoin1.command('domain-join') + removeparametersCreateVirtualMachineDomainJoin1.command('remove') .description($('Remove domain-join in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26212,9 +26212,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDomainJoin2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDomainJoin2 = catparametersCreateVirtualMachineDomainJoin2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineDomainJoin2 = parametersCreateVirtualMachineDomainJoin2.category('add') + var addparametersCreateVirtualMachineDomainJoin2 = parametersCreateVirtualMachineDomainJoin2.category('domain-join') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineDomainJoin2.command('domain-join') + addparametersCreateVirtualMachineDomainJoin2.command('add') .description($('Add domain-join in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26297,9 +26297,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineCredentials0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineCredentials0 = catparametersCreateVirtualMachineCredentials0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineCredentials0 = parametersCreateVirtualMachineCredentials0.category('set') + var setparametersCreateVirtualMachineCredentials0 = parametersCreateVirtualMachineCredentials0.category('credentials') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineCredentials0.command('credentials') + setparametersCreateVirtualMachineCredentials0.command('set') .description($('Set credentials in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26368,9 +26368,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineCredentials1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineCredentials1 = catparametersCreateVirtualMachineCredentials1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineCredentials1 = parametersCreateVirtualMachineCredentials1.category('remove') + var removeparametersCreateVirtualMachineCredentials1 = parametersCreateVirtualMachineCredentials1.category('credentials') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineCredentials1.command('credentials') + removeparametersCreateVirtualMachineCredentials1.command('remove') .description($('Remove credentials in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26423,9 +26423,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineCredentials2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineCredentials2 = catparametersCreateVirtualMachineCredentials2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineCredentials2 = parametersCreateVirtualMachineCredentials2.category('add') + var addparametersCreateVirtualMachineCredentials2 = parametersCreateVirtualMachineCredentials2.category('credentials') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineCredentials2.command('credentials') + addparametersCreateVirtualMachineCredentials2.command('add') .description($('Add credentials in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26497,9 +26497,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineProvisioning0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineProvisioning0 = catparametersCreateVirtualMachineProvisioning0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineProvisioning0 = parametersCreateVirtualMachineProvisioning0.category('set') + var setparametersCreateVirtualMachineProvisioning0 = parametersCreateVirtualMachineProvisioning0.category('provisioning') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineProvisioning0.command('provisioning') + setparametersCreateVirtualMachineProvisioning0.command('set') .description($('Set provisioning in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26546,9 +26546,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineProvisioning1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineProvisioning1 = catparametersCreateVirtualMachineProvisioning1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineProvisioning1 = parametersCreateVirtualMachineProvisioning1.category('remove') + var removeparametersCreateVirtualMachineProvisioning1 = parametersCreateVirtualMachineProvisioning1.category('provisioning') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineProvisioning1.command('provisioning') + removeparametersCreateVirtualMachineProvisioning1.command('remove') .description($('Remove provisioning in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26591,9 +26591,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineProvisioning2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineProvisioning2 = catparametersCreateVirtualMachineProvisioning2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineProvisioning2 = parametersCreateVirtualMachineProvisioning2.category('add') + var addparametersCreateVirtualMachineProvisioning2 = parametersCreateVirtualMachineProvisioning2.category('provisioning') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineProvisioning2.command('provisioning') + addparametersCreateVirtualMachineProvisioning2.command('add') .description($('Add provisioning in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26643,9 +26643,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineInputEndpoints0 = catparametersCreateVirtualMachineInputEndpoints0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineInputEndpoints0 = parametersCreateVirtualMachineInputEndpoints0.category('set') + var setparametersCreateVirtualMachineInputEndpoints0 = parametersCreateVirtualMachineInputEndpoints0.category('input-endpoints') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineInputEndpoints0.command('input-endpoints') + setparametersCreateVirtualMachineInputEndpoints0.command('set') .description($('Set input-endpoints in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26830,9 +26830,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineInputEndpoints1 = catparametersCreateVirtualMachineInputEndpoints1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineInputEndpoints1 = parametersCreateVirtualMachineInputEndpoints1.category('remove') + var removeparametersCreateVirtualMachineInputEndpoints1 = parametersCreateVirtualMachineInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineInputEndpoints1.command('input-endpoints') + removeparametersCreateVirtualMachineInputEndpoints1.command('remove') .description($('Remove input-endpoints in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -26936,9 +26936,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineInputEndpoints2 = catparametersCreateVirtualMachineInputEndpoints2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineInputEndpoints2 = parametersCreateVirtualMachineInputEndpoints2.category('add') + var addparametersCreateVirtualMachineInputEndpoints2 = parametersCreateVirtualMachineInputEndpoints2.category('input-endpoints') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineInputEndpoints2.command('input-endpoints') + addparametersCreateVirtualMachineInputEndpoints2.command('add') .description($('Add input-endpoints in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27121,9 +27121,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineEndpointAcl1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineEndpointAcl1 = catparametersCreateVirtualMachineEndpointAcl1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineEndpointAcl1 = parametersCreateVirtualMachineEndpointAcl1.category('remove') + var removeparametersCreateVirtualMachineEndpointAcl1 = parametersCreateVirtualMachineEndpointAcl1.category('endpoint-acl') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineEndpointAcl1.command('endpoint-acl') + removeparametersCreateVirtualMachineEndpointAcl1.command('remove') .description($('Remove endpoint-acl in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27167,9 +27167,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineEndpointAcl2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineEndpointAcl2 = catparametersCreateVirtualMachineEndpointAcl2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineEndpointAcl2 = parametersCreateVirtualMachineEndpointAcl2.category('add') + var addparametersCreateVirtualMachineEndpointAcl2 = parametersCreateVirtualMachineEndpointAcl2.category('endpoint-acl') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineEndpointAcl2.command('endpoint-acl') + addparametersCreateVirtualMachineEndpointAcl2.command('add') .description($('Add endpoint-acl in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27219,9 +27219,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineRules0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineRules0 = catparametersCreateVirtualMachineRules0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineRules0 = parametersCreateVirtualMachineRules0.category('set') + var setparametersCreateVirtualMachineRules0 = parametersCreateVirtualMachineRules0.category('rules') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineRules0.command('rules') + setparametersCreateVirtualMachineRules0.command('set') .description($('Set rules in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27307,9 +27307,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineRules1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineRules1 = catparametersCreateVirtualMachineRules1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineRules1 = parametersCreateVirtualMachineRules1.category('remove') + var removeparametersCreateVirtualMachineRules1 = parametersCreateVirtualMachineRules1.category('rules') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineRules1.command('rules') + removeparametersCreateVirtualMachineRules1.command('remove') .description($('Remove rules in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27369,9 +27369,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineRules2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineRules2 = catparametersCreateVirtualMachineRules2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineRules2 = parametersCreateVirtualMachineRules2.category('add') + var addparametersCreateVirtualMachineRules2 = parametersCreateVirtualMachineRules2.category('rules') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineRules2.command('rules') + addparametersCreateVirtualMachineRules2.command('add') .description($('Add rules in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27454,9 +27454,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineLoadBalancerProbe0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineLoadBalancerProbe0 = catparametersCreateVirtualMachineLoadBalancerProbe0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineLoadBalancerProbe0 = parametersCreateVirtualMachineLoadBalancerProbe0.category('set') + var setparametersCreateVirtualMachineLoadBalancerProbe0 = parametersCreateVirtualMachineLoadBalancerProbe0.category('load-balancer-probe') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineLoadBalancerProbe0.command('load-balancer-probe') + setparametersCreateVirtualMachineLoadBalancerProbe0.command('set') .description($('Set load-balancer-probe in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27548,9 +27548,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineLoadBalancerProbe1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineLoadBalancerProbe1 = catparametersCreateVirtualMachineLoadBalancerProbe1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineLoadBalancerProbe1 = parametersCreateVirtualMachineLoadBalancerProbe1.category('remove') + var removeparametersCreateVirtualMachineLoadBalancerProbe1 = parametersCreateVirtualMachineLoadBalancerProbe1.category('load-balancer-probe') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineLoadBalancerProbe1.command('load-balancer-probe') + removeparametersCreateVirtualMachineLoadBalancerProbe1.command('remove') .description($('Remove load-balancer-probe in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27614,9 +27614,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineLoadBalancerProbe2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineLoadBalancerProbe2 = catparametersCreateVirtualMachineLoadBalancerProbe2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineLoadBalancerProbe2 = parametersCreateVirtualMachineLoadBalancerProbe2.category('add') + var addparametersCreateVirtualMachineLoadBalancerProbe2 = parametersCreateVirtualMachineLoadBalancerProbe2.category('load-balancer-probe') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineLoadBalancerProbe2.command('load-balancer-probe') + addparametersCreateVirtualMachineLoadBalancerProbe2.command('add') .description($('Add load-balancer-probe in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27710,9 +27710,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineProtocol1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineProtocol1 = catparametersCreateVirtualMachineProtocol1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineProtocol1 = parametersCreateVirtualMachineProtocol1.category('remove') + var removeparametersCreateVirtualMachineProtocol1 = parametersCreateVirtualMachineProtocol1.category('protocol') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineProtocol1.command('protocol') + removeparametersCreateVirtualMachineProtocol1.command('remove') .description($('Remove protocol in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27745,9 +27745,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineProtocol2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineProtocol2 = catparametersCreateVirtualMachineProtocol2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineProtocol2 = parametersCreateVirtualMachineProtocol2.category('add') + var addparametersCreateVirtualMachineProtocol2 = parametersCreateVirtualMachineProtocol2.category('protocol') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineProtocol2.command('protocol') + addparametersCreateVirtualMachineProtocol2.command('add') .description($('Add protocol in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27786,9 +27786,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineNetworkInterfaces0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineNetworkInterfaces0 = catparametersCreateVirtualMachineNetworkInterfaces0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineNetworkInterfaces0 = parametersCreateVirtualMachineNetworkInterfaces0.category('set') + var setparametersCreateVirtualMachineNetworkInterfaces0 = parametersCreateVirtualMachineNetworkInterfaces0.category('network-interfaces') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineNetworkInterfaces0.command('network-interfaces') + setparametersCreateVirtualMachineNetworkInterfaces0.command('set') .description($('Set network-interfaces in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27873,9 +27873,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineNetworkInterfaces1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineNetworkInterfaces1 = catparametersCreateVirtualMachineNetworkInterfaces1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineNetworkInterfaces1 = parametersCreateVirtualMachineNetworkInterfaces1.category('remove') + var removeparametersCreateVirtualMachineNetworkInterfaces1 = parametersCreateVirtualMachineNetworkInterfaces1.category('network-interfaces') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineNetworkInterfaces1.command('network-interfaces') + removeparametersCreateVirtualMachineNetworkInterfaces1.command('remove') .description($('Remove network-interfaces in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -27934,9 +27934,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineNetworkInterfaces2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineNetworkInterfaces2 = catparametersCreateVirtualMachineNetworkInterfaces2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineNetworkInterfaces2 = parametersCreateVirtualMachineNetworkInterfaces2.category('add') + var addparametersCreateVirtualMachineNetworkInterfaces2 = parametersCreateVirtualMachineNetworkInterfaces2.category('network-interfaces') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineNetworkInterfaces2.command('network-interfaces') + addparametersCreateVirtualMachineNetworkInterfaces2.command('add') .description($('Add network-interfaces in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28019,9 +28019,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineIPConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineIPConfigurations0 = catparametersCreateVirtualMachineIPConfigurations0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineIPConfigurations0 = parametersCreateVirtualMachineIPConfigurations0.category('set') + var setparametersCreateVirtualMachineIPConfigurations0 = parametersCreateVirtualMachineIPConfigurations0.category('ip-configurations') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineIPConfigurations0.command('ip-configurations') + setparametersCreateVirtualMachineIPConfigurations0.command('set') .description($('Set ip-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28085,9 +28085,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineIPConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineIPConfigurations1 = catparametersCreateVirtualMachineIPConfigurations1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineIPConfigurations1 = parametersCreateVirtualMachineIPConfigurations1.category('remove') + var removeparametersCreateVirtualMachineIPConfigurations1 = parametersCreateVirtualMachineIPConfigurations1.category('ip-configurations') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineIPConfigurations1.command('ip-configurations') + removeparametersCreateVirtualMachineIPConfigurations1.command('remove') .description($('Remove ip-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28137,9 +28137,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineIPConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineIPConfigurations2 = catparametersCreateVirtualMachineIPConfigurations2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineIPConfigurations2 = parametersCreateVirtualMachineIPConfigurations2.category('add') + var addparametersCreateVirtualMachineIPConfigurations2 = parametersCreateVirtualMachineIPConfigurations2.category('ip-configurations') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineIPConfigurations2.command('ip-configurations') + addparametersCreateVirtualMachineIPConfigurations2.command('add') .description($('Add ip-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28200,9 +28200,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicIPs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicIPs0 = catparametersCreateVirtualMachinePublicIPs0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachinePublicIPs0 = parametersCreateVirtualMachinePublicIPs0.category('set') + var setparametersCreateVirtualMachinePublicIPs0 = parametersCreateVirtualMachinePublicIPs0.category('public-ip') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachinePublicIPs0.command('public-ip') + setparametersCreateVirtualMachinePublicIPs0.command('set') .description($('Set public-ip in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28276,9 +28276,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicIPs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicIPs1 = catparametersCreateVirtualMachinePublicIPs1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachinePublicIPs1 = parametersCreateVirtualMachinePublicIPs1.category('remove') + var removeparametersCreateVirtualMachinePublicIPs1 = parametersCreateVirtualMachinePublicIPs1.category('public-ip') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachinePublicIPs1.command('public-ip') + removeparametersCreateVirtualMachinePublicIPs1.command('remove') .description($('Remove public-ip in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28332,9 +28332,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicIPs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicIPs2 = catparametersCreateVirtualMachinePublicIPs2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachinePublicIPs2 = parametersCreateVirtualMachinePublicIPs2.category('add') + var addparametersCreateVirtualMachinePublicIPs2 = parametersCreateVirtualMachinePublicIPs2.category('public-ip') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachinePublicIPs2.command('public-ip') + addparametersCreateVirtualMachinePublicIPs2.command('add') .description($('Add public-ip in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28406,9 +28406,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineSshSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineSshSettings1 = catparametersCreateVirtualMachineSshSettings1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineSshSettings1 = parametersCreateVirtualMachineSshSettings1.category('remove') + var removeparametersCreateVirtualMachineSshSettings1 = parametersCreateVirtualMachineSshSettings1.category('ssh-settings') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineSshSettings1.command('ssh-settings') + removeparametersCreateVirtualMachineSshSettings1.command('remove') .description($('Remove ssh-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28456,9 +28456,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineSshSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineSshSettings2 = catparametersCreateVirtualMachineSshSettings2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineSshSettings2 = parametersCreateVirtualMachineSshSettings2.category('add') + var addparametersCreateVirtualMachineSshSettings2 = parametersCreateVirtualMachineSshSettings2.category('ssh-settings') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineSshSettings2.command('ssh-settings') + addparametersCreateVirtualMachineSshSettings2.command('add') .description($('Add ssh-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28519,9 +28519,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineKeyPairs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineKeyPairs0 = catparametersCreateVirtualMachineKeyPairs0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineKeyPairs0 = parametersCreateVirtualMachineKeyPairs0.category('set') + var setparametersCreateVirtualMachineKeyPairs0 = parametersCreateVirtualMachineKeyPairs0.category('key-pairs') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineKeyPairs0.command('key-pairs') + setparametersCreateVirtualMachineKeyPairs0.command('set') .description($('Set key-pairs in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28584,9 +28584,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineKeyPairs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineKeyPairs1 = catparametersCreateVirtualMachineKeyPairs1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineKeyPairs1 = parametersCreateVirtualMachineKeyPairs1.category('remove') + var removeparametersCreateVirtualMachineKeyPairs1 = parametersCreateVirtualMachineKeyPairs1.category('key-pairs') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineKeyPairs1.command('key-pairs') + removeparametersCreateVirtualMachineKeyPairs1.command('remove') .description($('Remove key-pairs in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28635,9 +28635,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineKeyPairs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineKeyPairs2 = catparametersCreateVirtualMachineKeyPairs2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineKeyPairs2 = parametersCreateVirtualMachineKeyPairs2.category('add') + var addparametersCreateVirtualMachineKeyPairs2 = parametersCreateVirtualMachineKeyPairs2.category('key-pairs') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineKeyPairs2.command('key-pairs') + addparametersCreateVirtualMachineKeyPairs2.command('add') .description($('Add key-pairs in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28698,9 +28698,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicKeys0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicKeys0 = catparametersCreateVirtualMachinePublicKeys0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachinePublicKeys0 = parametersCreateVirtualMachinePublicKeys0.category('set') + var setparametersCreateVirtualMachinePublicKeys0 = parametersCreateVirtualMachinePublicKeys0.category('public-keys') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachinePublicKeys0.command('public-keys') + setparametersCreateVirtualMachinePublicKeys0.command('set') .description($('Set public-keys in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28763,9 +28763,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicKeys1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicKeys1 = catparametersCreateVirtualMachinePublicKeys1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachinePublicKeys1 = parametersCreateVirtualMachinePublicKeys1.category('remove') + var removeparametersCreateVirtualMachinePublicKeys1 = parametersCreateVirtualMachinePublicKeys1.category('public-keys') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachinePublicKeys1.command('public-keys') + removeparametersCreateVirtualMachinePublicKeys1.command('remove') .description($('Remove public-keys in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28814,9 +28814,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachinePublicKeys2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachinePublicKeys2 = catparametersCreateVirtualMachinePublicKeys2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachinePublicKeys2 = parametersCreateVirtualMachinePublicKeys2.category('add') + var addparametersCreateVirtualMachinePublicKeys2 = parametersCreateVirtualMachinePublicKeys2.category('public-keys') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachinePublicKeys2.command('public-keys') + addparametersCreateVirtualMachinePublicKeys2.command('add') .description($('Add public-keys in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28877,9 +28877,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineStoredCertificateSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineStoredCertificateSettings0 = catparametersCreateVirtualMachineStoredCertificateSettings0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineStoredCertificateSettings0 = parametersCreateVirtualMachineStoredCertificateSettings0.category('set') + var setparametersCreateVirtualMachineStoredCertificateSettings0 = parametersCreateVirtualMachineStoredCertificateSettings0.category('stored-certificate-settings') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineStoredCertificateSettings0.command('stored-certificate-settings') + setparametersCreateVirtualMachineStoredCertificateSettings0.command('set') .description($('Set stored-certificate-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28942,9 +28942,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineStoredCertificateSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineStoredCertificateSettings1 = catparametersCreateVirtualMachineStoredCertificateSettings1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineStoredCertificateSettings1 = parametersCreateVirtualMachineStoredCertificateSettings1.category('remove') + var removeparametersCreateVirtualMachineStoredCertificateSettings1 = parametersCreateVirtualMachineStoredCertificateSettings1.category('stored-certificate-settings') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineStoredCertificateSettings1.command('stored-certificate-settings') + removeparametersCreateVirtualMachineStoredCertificateSettings1.command('remove') .description($('Remove stored-certificate-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -28993,9 +28993,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineStoredCertificateSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineStoredCertificateSettings2 = catparametersCreateVirtualMachineStoredCertificateSettings2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineStoredCertificateSettings2 = parametersCreateVirtualMachineStoredCertificateSettings2.category('add') + var addparametersCreateVirtualMachineStoredCertificateSettings2 = parametersCreateVirtualMachineStoredCertificateSettings2.category('stored-certificate-settings') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineStoredCertificateSettings2.command('stored-certificate-settings') + addparametersCreateVirtualMachineStoredCertificateSettings2.command('add') .description($('Add stored-certificate-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29056,9 +29056,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineSubnetNames0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineSubnetNames0 = catparametersCreateVirtualMachineSubnetNames0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineSubnetNames0 = parametersCreateVirtualMachineSubnetNames0.category('set') + var setparametersCreateVirtualMachineSubnetNames0 = parametersCreateVirtualMachineSubnetNames0.category('subnet-names') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineSubnetNames0.command('subnet-names') + setparametersCreateVirtualMachineSubnetNames0.command('set') .description($('Set subnet-names in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29099,9 +29099,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineSubnetNames1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineSubnetNames1 = catparametersCreateVirtualMachineSubnetNames1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineSubnetNames1 = parametersCreateVirtualMachineSubnetNames1.category('remove') + var removeparametersCreateVirtualMachineSubnetNames1 = parametersCreateVirtualMachineSubnetNames1.category('subnet-names') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineSubnetNames1.command('subnet-names') + removeparametersCreateVirtualMachineSubnetNames1.command('remove') .description($('Remove subnet-names in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29134,9 +29134,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineSubnetNames2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineSubnetNames2 = catparametersCreateVirtualMachineSubnetNames2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineSubnetNames2 = parametersCreateVirtualMachineSubnetNames2.category('add') + var addparametersCreateVirtualMachineSubnetNames2 = parametersCreateVirtualMachineSubnetNames2.category('subnet-names') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineSubnetNames2.command('subnet-names') + addparametersCreateVirtualMachineSubnetNames2.command('add') .description($('Add subnet-names in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29175,9 +29175,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineWindowsRemoteManagement1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineWindowsRemoteManagement1 = catparametersCreateVirtualMachineWindowsRemoteManagement1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineWindowsRemoteManagement1 = parametersCreateVirtualMachineWindowsRemoteManagement1.category('remove') + var removeparametersCreateVirtualMachineWindowsRemoteManagement1 = parametersCreateVirtualMachineWindowsRemoteManagement1.category('windows-remote-management') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineWindowsRemoteManagement1.command('windows-remote-management') + removeparametersCreateVirtualMachineWindowsRemoteManagement1.command('remove') .description($('Remove windows-remote-management in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29220,9 +29220,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineWindowsRemoteManagement2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineWindowsRemoteManagement2 = catparametersCreateVirtualMachineWindowsRemoteManagement2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineWindowsRemoteManagement2 = parametersCreateVirtualMachineWindowsRemoteManagement2.category('add') + var addparametersCreateVirtualMachineWindowsRemoteManagement2 = parametersCreateVirtualMachineWindowsRemoteManagement2.category('windows-remote-management') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineWindowsRemoteManagement2.command('windows-remote-management') + addparametersCreateVirtualMachineWindowsRemoteManagement2.command('add') .description($('Add windows-remote-management in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29272,9 +29272,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineListeners0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineListeners0 = catparametersCreateVirtualMachineListeners0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineListeners0 = parametersCreateVirtualMachineListeners0.category('set') + var setparametersCreateVirtualMachineListeners0 = parametersCreateVirtualMachineListeners0.category('listeners') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineListeners0.command('listeners') + setparametersCreateVirtualMachineListeners0.command('set') .description($('Set listeners in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29337,9 +29337,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineListeners1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineListeners1 = catparametersCreateVirtualMachineListeners1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineListeners1 = parametersCreateVirtualMachineListeners1.category('remove') + var removeparametersCreateVirtualMachineListeners1 = parametersCreateVirtualMachineListeners1.category('listeners') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineListeners1.command('listeners') + removeparametersCreateVirtualMachineListeners1.command('remove') .description($('Remove listeners in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29388,9 +29388,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineListeners2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineListeners2 = catparametersCreateVirtualMachineListeners2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineListeners2 = parametersCreateVirtualMachineListeners2.category('add') + var addparametersCreateVirtualMachineListeners2 = parametersCreateVirtualMachineListeners2.category('listeners') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineListeners2.command('listeners') + addparametersCreateVirtualMachineListeners2.command('add') .description($('Add listeners in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29451,9 +29451,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineListenerType1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineListenerType1 = catparametersCreateVirtualMachineListenerType1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineListenerType1 = parametersCreateVirtualMachineListenerType1.category('remove') + var removeparametersCreateVirtualMachineListenerType1 = parametersCreateVirtualMachineListenerType1.category('listener-type') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineListenerType1.command('listener-type') + removeparametersCreateVirtualMachineListenerType1.command('remove') .description($('Remove listener-type in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29486,9 +29486,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineListenerType2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineListenerType2 = catparametersCreateVirtualMachineListenerType2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineListenerType2 = parametersCreateVirtualMachineListenerType2.category('add') + var addparametersCreateVirtualMachineListenerType2 = parametersCreateVirtualMachineListenerType2.category('listener-type') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineListenerType2.command('listener-type') + addparametersCreateVirtualMachineListenerType2.command('add') .description($('Add listener-type in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29527,9 +29527,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataVirtualHardDisks0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataVirtualHardDisks0 = catparametersCreateVirtualMachineDataVirtualHardDisks0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineDataVirtualHardDisks0 = parametersCreateVirtualMachineDataVirtualHardDisks0.category('set') + var setparametersCreateVirtualMachineDataVirtualHardDisks0 = parametersCreateVirtualMachineDataVirtualHardDisks0.category('data-virtual-hard-disks') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineDataVirtualHardDisks0.command('data-virtual-hard-disks') + setparametersCreateVirtualMachineDataVirtualHardDisks0.command('set') .description($('Set data-virtual-hard-disks in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29657,9 +29657,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataVirtualHardDisks1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataVirtualHardDisks1 = catparametersCreateVirtualMachineDataVirtualHardDisks1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineDataVirtualHardDisks1 = parametersCreateVirtualMachineDataVirtualHardDisks1.category('remove') + var removeparametersCreateVirtualMachineDataVirtualHardDisks1 = parametersCreateVirtualMachineDataVirtualHardDisks1.category('data-virtual-hard-disks') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineDataVirtualHardDisks1.command('data-virtual-hard-disks') + removeparametersCreateVirtualMachineDataVirtualHardDisks1.command('remove') .description($('Remove data-virtual-hard-disks in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29737,9 +29737,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataVirtualHardDisks2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataVirtualHardDisks2 = catparametersCreateVirtualMachineDataVirtualHardDisks2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineDataVirtualHardDisks2 = parametersCreateVirtualMachineDataVirtualHardDisks2.category('add') + var addparametersCreateVirtualMachineDataVirtualHardDisks2 = parametersCreateVirtualMachineDataVirtualHardDisks2.category('data-virtual-hard-disks') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineDataVirtualHardDisks2.command('data-virtual-hard-disks') + addparametersCreateVirtualMachineDataVirtualHardDisks2.command('add') .description($('Add data-virtual-hard-disks in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29866,9 +29866,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDebugSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDebugSettings0 = catparametersCreateVirtualMachineDebugSettings0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineDebugSettings0 = parametersCreateVirtualMachineDebugSettings0.category('set') + var setparametersCreateVirtualMachineDebugSettings0 = parametersCreateVirtualMachineDebugSettings0.category('debug-settings') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineDebugSettings0.command('debug-settings') + setparametersCreateVirtualMachineDebugSettings0.command('set') .description($('Set debug-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29936,9 +29936,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDebugSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDebugSettings1 = catparametersCreateVirtualMachineDebugSettings1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineDebugSettings1 = parametersCreateVirtualMachineDebugSettings1.category('remove') + var removeparametersCreateVirtualMachineDebugSettings1 = parametersCreateVirtualMachineDebugSettings1.category('debug-settings') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineDebugSettings1.command('debug-settings') + removeparametersCreateVirtualMachineDebugSettings1.command('remove') .description($('Remove debug-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -29990,9 +29990,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDebugSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDebugSettings2 = catparametersCreateVirtualMachineDebugSettings2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineDebugSettings2 = parametersCreateVirtualMachineDebugSettings2.category('add') + var addparametersCreateVirtualMachineDebugSettings2 = parametersCreateVirtualMachineDebugSettings2.category('debug-settings') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineDebugSettings2.command('debug-settings') + addparametersCreateVirtualMachineDebugSettings2.command('add') .description($('Add debug-settings in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30064,9 +30064,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSVirtualHardDisk0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSVirtualHardDisk0 = catparametersCreateVirtualMachineOSVirtualHardDisk0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineOSVirtualHardDisk0 = parametersCreateVirtualMachineOSVirtualHardDisk0.category('set') + var setparametersCreateVirtualMachineOSVirtualHardDisk0 = parametersCreateVirtualMachineOSVirtualHardDisk0.category('os-virtual-hard-disk') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineOSVirtualHardDisk0.command('os-virtual-hard-disk') + setparametersCreateVirtualMachineOSVirtualHardDisk0.command('set') .description($('Set os-virtual-hard-disk in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30200,9 +30200,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSVirtualHardDisk1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSVirtualHardDisk1 = catparametersCreateVirtualMachineOSVirtualHardDisk1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineOSVirtualHardDisk1 = parametersCreateVirtualMachineOSVirtualHardDisk1.category('remove') + var removeparametersCreateVirtualMachineOSVirtualHardDisk1 = parametersCreateVirtualMachineOSVirtualHardDisk1.category('os-virtual-hard-disk') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineOSVirtualHardDisk1.command('os-virtual-hard-disk') + removeparametersCreateVirtualMachineOSVirtualHardDisk1.command('remove') .description($('Remove os-virtual-hard-disk in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30284,9 +30284,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSVirtualHardDisk2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSVirtualHardDisk2 = catparametersCreateVirtualMachineOSVirtualHardDisk2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineOSVirtualHardDisk2 = parametersCreateVirtualMachineOSVirtualHardDisk2.category('add') + var addparametersCreateVirtualMachineOSVirtualHardDisk2 = parametersCreateVirtualMachineOSVirtualHardDisk2.category('os-virtual-hard-disk') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineOSVirtualHardDisk2.command('os-virtual-hard-disk') + addparametersCreateVirtualMachineOSVirtualHardDisk2.command('add') .description($('Add os-virtual-hard-disk in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30424,9 +30424,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionReferences0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionReferences0 = catparametersCreateVirtualMachineResourceExtensionReferences0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineResourceExtensionReferences0 = parametersCreateVirtualMachineResourceExtensionReferences0.category('set') + var setparametersCreateVirtualMachineResourceExtensionReferences0 = parametersCreateVirtualMachineResourceExtensionReferences0.category('resource-extension-references') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineResourceExtensionReferences0.command('resource-extension-references') + setparametersCreateVirtualMachineResourceExtensionReferences0.command('set') .description($('Set resource-extension-references in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30544,9 +30544,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionReferences1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionReferences1 = catparametersCreateVirtualMachineResourceExtensionReferences1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineResourceExtensionReferences1 = parametersCreateVirtualMachineResourceExtensionReferences1.category('remove') + var removeparametersCreateVirtualMachineResourceExtensionReferences1 = parametersCreateVirtualMachineResourceExtensionReferences1.category('resource-extension-references') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineResourceExtensionReferences1.command('resource-extension-references') + removeparametersCreateVirtualMachineResourceExtensionReferences1.command('remove') .description($('Remove resource-extension-references in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30619,9 +30619,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionReferences2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionReferences2 = catparametersCreateVirtualMachineResourceExtensionReferences2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineResourceExtensionReferences2 = parametersCreateVirtualMachineResourceExtensionReferences2.category('add') + var addparametersCreateVirtualMachineResourceExtensionReferences2 = parametersCreateVirtualMachineResourceExtensionReferences2.category('resource-extension-references') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineResourceExtensionReferences2.command('resource-extension-references') + addparametersCreateVirtualMachineResourceExtensionReferences2.command('add') .description($('Add resource-extension-references in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30738,9 +30738,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionParameterValues0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionParameterValues0 = catparametersCreateVirtualMachineResourceExtensionParameterValues0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineResourceExtensionParameterValues0 = parametersCreateVirtualMachineResourceExtensionParameterValues0.category('set') + var setparametersCreateVirtualMachineResourceExtensionParameterValues0 = parametersCreateVirtualMachineResourceExtensionParameterValues0.category('resource-extension-parameter-values') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineResourceExtensionParameterValues0.command('resource-extension-parameter-values') + setparametersCreateVirtualMachineResourceExtensionParameterValues0.command('set') .description($('Set resource-extension-parameter-values in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30814,9 +30814,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionParameterValues1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionParameterValues1 = catparametersCreateVirtualMachineResourceExtensionParameterValues1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineResourceExtensionParameterValues1 = parametersCreateVirtualMachineResourceExtensionParameterValues1.category('remove') + var removeparametersCreateVirtualMachineResourceExtensionParameterValues1 = parametersCreateVirtualMachineResourceExtensionParameterValues1.category('resource-extension-parameter-values') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineResourceExtensionParameterValues1.command('resource-extension-parameter-values') + removeparametersCreateVirtualMachineResourceExtensionParameterValues1.command('remove') .description($('Remove resource-extension-parameter-values in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30870,9 +30870,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineResourceExtensionParameterValues2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineResourceExtensionParameterValues2 = catparametersCreateVirtualMachineResourceExtensionParameterValues2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineResourceExtensionParameterValues2 = parametersCreateVirtualMachineResourceExtensionParameterValues2.category('add') + var addparametersCreateVirtualMachineResourceExtensionParameterValues2 = parametersCreateVirtualMachineResourceExtensionParameterValues2.category('resource-extension-parameter-values') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineResourceExtensionParameterValues2.command('resource-extension-parameter-values') + addparametersCreateVirtualMachineResourceExtensionParameterValues2.command('add') .description($('Add resource-extension-parameter-values in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30944,9 +30944,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageInput1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineVMImageInput1 = catparametersCreateVirtualMachineVMImageInput1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineVMImageInput1 = parametersCreateVirtualMachineVMImageInput1.category('remove') + var removeparametersCreateVirtualMachineVMImageInput1 = parametersCreateVirtualMachineVMImageInput1.category('vm-image-input') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineVMImageInput1.command('vm-image-input') + removeparametersCreateVirtualMachineVMImageInput1.command('remove') .description($('Remove vm-image-input in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "vMImageInput" : {\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -30993,9 +30993,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageInput2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineVMImageInput2 = catparametersCreateVirtualMachineVMImageInput2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineVMImageInput2 = parametersCreateVirtualMachineVMImageInput2.category('add') + var addparametersCreateVirtualMachineVMImageInput2 = parametersCreateVirtualMachineVMImageInput2.category('vm-image-input') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineVMImageInput2.command('vm-image-input') + addparametersCreateVirtualMachineVMImageInput2.command('add') .description($('Add vm-image-input in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "vMImageInput" : {\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31056,9 +31056,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataDiskConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataDiskConfigurations0 = catparametersCreateVirtualMachineDataDiskConfigurations0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineDataDiskConfigurations0 = parametersCreateVirtualMachineDataDiskConfigurations0.category('set') + var setparametersCreateVirtualMachineDataDiskConfigurations0 = parametersCreateVirtualMachineDataDiskConfigurations0.category('data-disk-configurations') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineDataDiskConfigurations0.command('data-disk-configurations') + setparametersCreateVirtualMachineDataDiskConfigurations0.command('set') .description($('Set data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31120,9 +31120,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataDiskConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataDiskConfigurations1 = catparametersCreateVirtualMachineDataDiskConfigurations1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineDataDiskConfigurations1 = parametersCreateVirtualMachineDataDiskConfigurations1.category('remove') + var removeparametersCreateVirtualMachineDataDiskConfigurations1 = parametersCreateVirtualMachineDataDiskConfigurations1.category('data-disk-configurations') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineDataDiskConfigurations1.command('data-disk-configurations') + removeparametersCreateVirtualMachineDataDiskConfigurations1.command('remove') .description($('Remove data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31170,9 +31170,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineDataDiskConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineDataDiskConfigurations2 = catparametersCreateVirtualMachineDataDiskConfigurations2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineDataDiskConfigurations2 = parametersCreateVirtualMachineDataDiskConfigurations2.category('add') + var addparametersCreateVirtualMachineDataDiskConfigurations2 = parametersCreateVirtualMachineDataDiskConfigurations2.category('data-disk-configurations') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineDataDiskConfigurations2.command('data-disk-configurations') + addparametersCreateVirtualMachineDataDiskConfigurations2.command('add') .description($('Add data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31233,9 +31233,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSDiskConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSDiskConfiguration0 = catparametersCreateVirtualMachineOSDiskConfiguration0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateVirtualMachineOSDiskConfiguration0 = parametersCreateVirtualMachineOSDiskConfiguration0.category('set') + var setparametersCreateVirtualMachineOSDiskConfiguration0 = parametersCreateVirtualMachineOSDiskConfiguration0.category('os-disk-configuration') .description($('Commands to set components of virtual-machine in create-parameters file.')); - setparametersCreateVirtualMachineOSDiskConfiguration0.command('os-disk-configuration') + setparametersCreateVirtualMachineOSDiskConfiguration0.command('set') .description($('Set os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31281,9 +31281,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSDiskConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSDiskConfiguration1 = catparametersCreateVirtualMachineOSDiskConfiguration1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateVirtualMachineOSDiskConfiguration1 = parametersCreateVirtualMachineOSDiskConfiguration1.category('remove') + var removeparametersCreateVirtualMachineOSDiskConfiguration1 = parametersCreateVirtualMachineOSDiskConfiguration1.category('os-disk-configuration') .description($('Commands to remove components of virtual-machine in create-parameters file.')); - removeparametersCreateVirtualMachineOSDiskConfiguration1.command('os-disk-configuration') + removeparametersCreateVirtualMachineOSDiskConfiguration1.command('remove') .description($('Remove os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31325,9 +31325,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSDiskConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateVirtualMachineOSDiskConfiguration2 = catparametersCreateVirtualMachineOSDiskConfiguration2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateVirtualMachineOSDiskConfiguration2 = parametersCreateVirtualMachineOSDiskConfiguration2.category('add') + var addparametersCreateVirtualMachineOSDiskConfiguration2 = parametersCreateVirtualMachineOSDiskConfiguration2.category('os-disk-configuration') .description($('Commands to add components of virtual-machine in create-parameters file.')); - addparametersCreateVirtualMachineOSDiskConfiguration2.command('os-disk-configuration') + addparametersCreateVirtualMachineOSDiskConfiguration2.command('add') .description($('Add os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31707,9 +31707,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0 = catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0.category('set') + var setparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0.category('virtual-machine-create-deployment-parameters') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0.command('virtual-machine-create-deployment-parameters') + setparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters0.command('set') .description($('Set virtual-machine-create-deployment-parameters in create-deployment-parameters string or files, e.g. \r\n{\r\n "deploymentSlot":0,\r\n "dnsSettings":{\r\n "dnsServers":[\r\n {\r\n "address":"",\r\n "name":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "loadBalancers":[\r\n {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ],\r\n "name":"",\r\n "reservedIPName":"",\r\n "roles":[\r\n {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ],\r\n "virtualNetworkName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31832,9 +31832,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1 = catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1.category('remove') + var removeparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1.category('virtual-machine-create-deployment-parameters') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1.command('virtual-machine-create-deployment-parameters') + removeparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters1.command('remove') .description($('Remove virtual-machine-create-deployment-parameters in create-deployment-parameters string or files, e.g. \r\n{\r\n "deploymentSlot":0,\r\n "dnsSettings":{\r\n "dnsServers":[\r\n {\r\n "address":"",\r\n "name":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "loadBalancers":[\r\n {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ],\r\n "name":"",\r\n "reservedIPName":"",\r\n "roles":[\r\n {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ],\r\n "virtualNetworkName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -31911,9 +31911,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2 = catparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2.category('add') + var addparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2 = parametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2.category('virtual-machine-create-deployment-parameters') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2.command('virtual-machine-create-deployment-parameters') + addparametersCreateDeploymentVirtualMachineVirtualMachineCreateDeploymentParameters2.command('add') .description($('Add virtual-machine-create-deployment-parameters in create-deployment-parameters string or files, e.g. \r\n{\r\n "deploymentSlot":0,\r\n "dnsSettings":{\r\n "dnsServers":[\r\n {\r\n "address":"",\r\n "name":""\r\n }\r\n ]\r\n },\r\n "label":"",\r\n "loadBalancers":[\r\n {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ],\r\n "name":"",\r\n "reservedIPName":"",\r\n "roles":[\r\n {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ],\r\n "virtualNetworkName":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32040,9 +32040,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDeploymentSlot1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDeploymentSlot1 = catparametersCreateDeploymentVirtualMachineDeploymentSlot1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDeploymentSlot1 = parametersCreateDeploymentVirtualMachineDeploymentSlot1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDeploymentSlot1 = parametersCreateDeploymentVirtualMachineDeploymentSlot1.category('deployment-slot') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDeploymentSlot1.command('deployment-slot') + removeparametersCreateDeploymentVirtualMachineDeploymentSlot1.command('remove') .description($('Remove deployment-slot in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "deploymentSlot" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32072,9 +32072,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDeploymentSlot2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDeploymentSlot2 = catparametersCreateDeploymentVirtualMachineDeploymentSlot2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDeploymentSlot2 = parametersCreateDeploymentVirtualMachineDeploymentSlot2.category('add') + var addparametersCreateDeploymentVirtualMachineDeploymentSlot2 = parametersCreateDeploymentVirtualMachineDeploymentSlot2.category('deployment-slot') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDeploymentSlot2.command('deployment-slot') + addparametersCreateDeploymentVirtualMachineDeploymentSlot2.command('add') .description($('Add deployment-slot in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "deploymentSlot" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32113,9 +32113,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDnsSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDnsSettings1 = catparametersCreateDeploymentVirtualMachineDnsSettings1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDnsSettings1 = parametersCreateDeploymentVirtualMachineDnsSettings1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDnsSettings1 = parametersCreateDeploymentVirtualMachineDnsSettings1.category('dns-settings') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDnsSettings1.command('dns-settings') + removeparametersCreateDeploymentVirtualMachineDnsSettings1.command('remove') .description($('Remove dns-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dnsSettings" : {\r\n "dnsServers":[\r\n {\r\n "address":"",\r\n "name":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32157,9 +32157,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDnsSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDnsSettings2 = catparametersCreateDeploymentVirtualMachineDnsSettings2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDnsSettings2 = parametersCreateDeploymentVirtualMachineDnsSettings2.category('add') + var addparametersCreateDeploymentVirtualMachineDnsSettings2 = parametersCreateDeploymentVirtualMachineDnsSettings2.category('dns-settings') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDnsSettings2.command('dns-settings') + addparametersCreateDeploymentVirtualMachineDnsSettings2.command('add') .description($('Add dns-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dnsSettings" : {\r\n "dnsServers":[\r\n {\r\n "address":"",\r\n "name":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32209,9 +32209,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDnsServers0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDnsServers0 = catparametersCreateDeploymentVirtualMachineDnsServers0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineDnsServers0 = parametersCreateDeploymentVirtualMachineDnsServers0.category('set') + var setparametersCreateDeploymentVirtualMachineDnsServers0 = parametersCreateDeploymentVirtualMachineDnsServers0.category('dns-servers') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineDnsServers0.command('dns-servers') + setparametersCreateDeploymentVirtualMachineDnsServers0.command('set') .description($('Set dns-servers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dnsServers" : {\r\n "address":"",\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32273,9 +32273,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDnsServers1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDnsServers1 = catparametersCreateDeploymentVirtualMachineDnsServers1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDnsServers1 = parametersCreateDeploymentVirtualMachineDnsServers1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDnsServers1 = parametersCreateDeploymentVirtualMachineDnsServers1.category('dns-servers') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDnsServers1.command('dns-servers') + removeparametersCreateDeploymentVirtualMachineDnsServers1.command('remove') .description($('Remove dns-servers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dnsServers" : {\r\n "address":"",\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32323,9 +32323,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDnsServers2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDnsServers2 = catparametersCreateDeploymentVirtualMachineDnsServers2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDnsServers2 = parametersCreateDeploymentVirtualMachineDnsServers2.category('add') + var addparametersCreateDeploymentVirtualMachineDnsServers2 = parametersCreateDeploymentVirtualMachineDnsServers2.category('dns-servers') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDnsServers2.command('dns-servers') + addparametersCreateDeploymentVirtualMachineDnsServers2.command('add') .description($('Add dns-servers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dnsServers" : {\r\n "address":"",\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32386,9 +32386,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancers0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancers0 = catparametersCreateDeploymentVirtualMachineLoadBalancers0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineLoadBalancers0 = parametersCreateDeploymentVirtualMachineLoadBalancers0.category('set') + var setparametersCreateDeploymentVirtualMachineLoadBalancers0 = parametersCreateDeploymentVirtualMachineLoadBalancers0.category('load-balancers') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineLoadBalancers0.command('load-balancers') + setparametersCreateDeploymentVirtualMachineLoadBalancers0.command('set') .description($('Set load-balancers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancers" : {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32450,9 +32450,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancers1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancers1 = catparametersCreateDeploymentVirtualMachineLoadBalancers1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineLoadBalancers1 = parametersCreateDeploymentVirtualMachineLoadBalancers1.category('remove') + var removeparametersCreateDeploymentVirtualMachineLoadBalancers1 = parametersCreateDeploymentVirtualMachineLoadBalancers1.category('load-balancers') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineLoadBalancers1.command('load-balancers') + removeparametersCreateDeploymentVirtualMachineLoadBalancers1.command('remove') .description($('Remove load-balancers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancers" : {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32500,9 +32500,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancers2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancers2 = catparametersCreateDeploymentVirtualMachineLoadBalancers2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineLoadBalancers2 = parametersCreateDeploymentVirtualMachineLoadBalancers2.category('add') + var addparametersCreateDeploymentVirtualMachineLoadBalancers2 = parametersCreateDeploymentVirtualMachineLoadBalancers2.category('load-balancers') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineLoadBalancers2.command('load-balancers') + addparametersCreateDeploymentVirtualMachineLoadBalancers2.command('add') .description($('Add load-balancers in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancers" : {\r\n "frontendIPConfiguration":{\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n },\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32563,9 +32563,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineFrontendIPConfiguration0 = catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration0.category('set') + var setparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration0.category('frontend-ip-configuration') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0.command('frontend-ip-configuration') + setparametersCreateDeploymentVirtualMachineFrontendIPConfiguration0.command('set') .description($('Set frontend-ip-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32634,9 +32634,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineFrontendIPConfiguration1 = catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration1.category('remove') + var removeparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration1.category('frontend-ip-configuration') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1.command('frontend-ip-configuration') + removeparametersCreateDeploymentVirtualMachineFrontendIPConfiguration1.command('remove') .description($('Remove frontend-ip-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32689,9 +32689,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineFrontendIPConfiguration2 = catparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration2.category('add') + var addparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2 = parametersCreateDeploymentVirtualMachineFrontendIPConfiguration2.category('frontend-ip-configuration') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2.command('frontend-ip-configuration') + addparametersCreateDeploymentVirtualMachineFrontendIPConfiguration2.command('add') .description($('Add frontend-ip-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "frontendIPConfiguration" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":"",\r\n "type":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32763,9 +32763,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRoles0 = catparametersCreateDeploymentVirtualMachineRoles0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineRoles0 = parametersCreateDeploymentVirtualMachineRoles0.category('set') + var setparametersCreateDeploymentVirtualMachineRoles0 = parametersCreateDeploymentVirtualMachineRoles0.category('roles') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineRoles0.command('roles') + setparametersCreateDeploymentVirtualMachineRoles0.command('set') .description($('Set roles in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -32982,9 +32982,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRoles1 = catparametersCreateDeploymentVirtualMachineRoles1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineRoles1 = parametersCreateDeploymentVirtualMachineRoles1.category('remove') + var removeparametersCreateDeploymentVirtualMachineRoles1 = parametersCreateDeploymentVirtualMachineRoles1.category('roles') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineRoles1.command('roles') + removeparametersCreateDeploymentVirtualMachineRoles1.command('remove') .description($('Remove roles in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -33102,9 +33102,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRoles2 = catparametersCreateDeploymentVirtualMachineRoles2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineRoles2 = parametersCreateDeploymentVirtualMachineRoles2.category('add') + var addparametersCreateDeploymentVirtualMachineRoles2 = parametersCreateDeploymentVirtualMachineRoles2.category('roles') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineRoles2.command('roles') + addparametersCreateDeploymentVirtualMachineRoles2.command('add') .description($('Add roles in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : {\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "defaultWinRmCertificateThumbprint":"",\r\n "label":"",\r\n "mediaLocation":"",\r\n "oSVersion":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":"",\r\n "roleType":"",\r\n "vMImageInput":{\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n },\r\n "vMImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -33320,9 +33320,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineConfigurationSets0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineConfigurationSets0 = catparametersCreateDeploymentVirtualMachineConfigurationSets0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineConfigurationSets0 = parametersCreateDeploymentVirtualMachineConfigurationSets0.category('set') + var setparametersCreateDeploymentVirtualMachineConfigurationSets0 = parametersCreateDeploymentVirtualMachineConfigurationSets0.category('configuration-sets') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineConfigurationSets0.command('configuration-sets') + setparametersCreateDeploymentVirtualMachineConfigurationSets0.command('set') .description($('Set configuration-sets in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -33630,9 +33630,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineConfigurationSets1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineConfigurationSets1 = catparametersCreateDeploymentVirtualMachineConfigurationSets1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineConfigurationSets1 = parametersCreateDeploymentVirtualMachineConfigurationSets1.category('remove') + var removeparametersCreateDeploymentVirtualMachineConfigurationSets1 = parametersCreateDeploymentVirtualMachineConfigurationSets1.category('configuration-sets') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineConfigurationSets1.command('configuration-sets') + removeparametersCreateDeploymentVirtualMachineConfigurationSets1.command('remove') .description($('Remove configuration-sets in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -33791,9 +33791,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineConfigurationSets2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineConfigurationSets2 = catparametersCreateDeploymentVirtualMachineConfigurationSets2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineConfigurationSets2 = parametersCreateDeploymentVirtualMachineConfigurationSets2.category('add') + var addparametersCreateDeploymentVirtualMachineConfigurationSets2 = parametersCreateDeploymentVirtualMachineConfigurationSets2.category('configuration-sets') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineConfigurationSets2.command('configuration-sets') + addparametersCreateDeploymentVirtualMachineConfigurationSets2.command('add') .description($('Add configuration-sets in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34099,9 +34099,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineAdditionalUnattendContent1 = catparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1 = parametersCreateDeploymentVirtualMachineAdditionalUnattendContent1.category('remove') + var removeparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1 = parametersCreateDeploymentVirtualMachineAdditionalUnattendContent1.category('additional-unattend-content') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1.command('additional-unattend-content') + removeparametersCreateDeploymentVirtualMachineAdditionalUnattendContent1.command('remove') .description($('Remove additional-unattend-content in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34145,9 +34145,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineAdditionalUnattendContent2 = catparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2 = parametersCreateDeploymentVirtualMachineAdditionalUnattendContent2.category('add') + var addparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2 = parametersCreateDeploymentVirtualMachineAdditionalUnattendContent2.category('additional-unattend-content') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2.command('additional-unattend-content') + addparametersCreateDeploymentVirtualMachineAdditionalUnattendContent2.command('add') .description($('Add additional-unattend-content in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34197,9 +34197,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendPasses0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendPasses0 = catparametersCreateDeploymentVirtualMachineUnattendPasses0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineUnattendPasses0 = parametersCreateDeploymentVirtualMachineUnattendPasses0.category('set') + var setparametersCreateDeploymentVirtualMachineUnattendPasses0 = parametersCreateDeploymentVirtualMachineUnattendPasses0.category('unattend-passes') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineUnattendPasses0.command('unattend-passes') + setparametersCreateDeploymentVirtualMachineUnattendPasses0.command('set') .description($('Set unattend-passes in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34263,9 +34263,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendPasses1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendPasses1 = catparametersCreateDeploymentVirtualMachineUnattendPasses1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineUnattendPasses1 = parametersCreateDeploymentVirtualMachineUnattendPasses1.category('remove') + var removeparametersCreateDeploymentVirtualMachineUnattendPasses1 = parametersCreateDeploymentVirtualMachineUnattendPasses1.category('unattend-passes') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineUnattendPasses1.command('unattend-passes') + removeparametersCreateDeploymentVirtualMachineUnattendPasses1.command('remove') .description($('Remove unattend-passes in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34315,9 +34315,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendPasses2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendPasses2 = catparametersCreateDeploymentVirtualMachineUnattendPasses2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineUnattendPasses2 = parametersCreateDeploymentVirtualMachineUnattendPasses2.category('add') + var addparametersCreateDeploymentVirtualMachineUnattendPasses2 = parametersCreateDeploymentVirtualMachineUnattendPasses2.category('unattend-passes') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineUnattendPasses2.command('unattend-passes') + addparametersCreateDeploymentVirtualMachineUnattendPasses2.command('add') .description($('Add unattend-passes in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34378,9 +34378,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponents0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponents0 = catparametersCreateDeploymentVirtualMachineUnattendComponents0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineUnattendComponents0 = parametersCreateDeploymentVirtualMachineUnattendComponents0.category('set') + var setparametersCreateDeploymentVirtualMachineUnattendComponents0 = parametersCreateDeploymentVirtualMachineUnattendComponents0.category('unattend-components') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineUnattendComponents0.command('unattend-components') + setparametersCreateDeploymentVirtualMachineUnattendComponents0.command('set') .description($('Set unattend-components in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34445,9 +34445,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponents1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponents1 = catparametersCreateDeploymentVirtualMachineUnattendComponents1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineUnattendComponents1 = parametersCreateDeploymentVirtualMachineUnattendComponents1.category('remove') + var removeparametersCreateDeploymentVirtualMachineUnattendComponents1 = parametersCreateDeploymentVirtualMachineUnattendComponents1.category('unattend-components') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineUnattendComponents1.command('unattend-components') + removeparametersCreateDeploymentVirtualMachineUnattendComponents1.command('remove') .description($('Remove unattend-components in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34498,9 +34498,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponents2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponents2 = catparametersCreateDeploymentVirtualMachineUnattendComponents2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineUnattendComponents2 = parametersCreateDeploymentVirtualMachineUnattendComponents2.category('add') + var addparametersCreateDeploymentVirtualMachineUnattendComponents2 = parametersCreateDeploymentVirtualMachineUnattendComponents2.category('unattend-components') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineUnattendComponents2.command('unattend-components') + addparametersCreateDeploymentVirtualMachineUnattendComponents2.command('add') .description($('Add unattend-components in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34561,9 +34561,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponentSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponentSettings0 = catparametersCreateDeploymentVirtualMachineUnattendComponentSettings0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineUnattendComponentSettings0 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings0.category('set') + var setparametersCreateDeploymentVirtualMachineUnattendComponentSettings0 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings0.category('unattend-component-settings') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineUnattendComponentSettings0.command('unattend-component-settings') + setparametersCreateDeploymentVirtualMachineUnattendComponentSettings0.command('set') .description($('Set unattend-component-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34629,9 +34629,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponentSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponentSettings1 = catparametersCreateDeploymentVirtualMachineUnattendComponentSettings1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineUnattendComponentSettings1 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings1.category('remove') + var removeparametersCreateDeploymentVirtualMachineUnattendComponentSettings1 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings1.category('unattend-component-settings') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineUnattendComponentSettings1.command('unattend-component-settings') + removeparametersCreateDeploymentVirtualMachineUnattendComponentSettings1.command('remove') .description($('Remove unattend-component-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34683,9 +34683,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineUnattendComponentSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineUnattendComponentSettings2 = catparametersCreateDeploymentVirtualMachineUnattendComponentSettings2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineUnattendComponentSettings2 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings2.category('add') + var addparametersCreateDeploymentVirtualMachineUnattendComponentSettings2 = parametersCreateDeploymentVirtualMachineUnattendComponentSettings2.category('unattend-component-settings') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineUnattendComponentSettings2.command('unattend-component-settings') + addparametersCreateDeploymentVirtualMachineUnattendComponentSettings2.command('add') .description($('Add unattend-component-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34746,9 +34746,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDomainJoin0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDomainJoin0 = catparametersCreateDeploymentVirtualMachineDomainJoin0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineDomainJoin0 = parametersCreateDeploymentVirtualMachineDomainJoin0.category('set') + var setparametersCreateDeploymentVirtualMachineDomainJoin0 = parametersCreateDeploymentVirtualMachineDomainJoin0.category('domain-join') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineDomainJoin0.command('domain-join') + setparametersCreateDeploymentVirtualMachineDomainJoin0.command('set') .description($('Set domain-join in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34829,9 +34829,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDomainJoin1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDomainJoin1 = catparametersCreateDeploymentVirtualMachineDomainJoin1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDomainJoin1 = parametersCreateDeploymentVirtualMachineDomainJoin1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDomainJoin1 = parametersCreateDeploymentVirtualMachineDomainJoin1.category('domain-join') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDomainJoin1.command('domain-join') + removeparametersCreateDeploymentVirtualMachineDomainJoin1.command('remove') .description($('Remove domain-join in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34890,9 +34890,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDomainJoin2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDomainJoin2 = catparametersCreateDeploymentVirtualMachineDomainJoin2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDomainJoin2 = parametersCreateDeploymentVirtualMachineDomainJoin2.category('add') + var addparametersCreateDeploymentVirtualMachineDomainJoin2 = parametersCreateDeploymentVirtualMachineDomainJoin2.category('domain-join') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDomainJoin2.command('domain-join') + addparametersCreateDeploymentVirtualMachineDomainJoin2.command('add') .description($('Add domain-join in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -34975,9 +34975,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineCredentials0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineCredentials0 = catparametersCreateDeploymentVirtualMachineCredentials0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineCredentials0 = parametersCreateDeploymentVirtualMachineCredentials0.category('set') + var setparametersCreateDeploymentVirtualMachineCredentials0 = parametersCreateDeploymentVirtualMachineCredentials0.category('credentials') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineCredentials0.command('credentials') + setparametersCreateDeploymentVirtualMachineCredentials0.command('set') .description($('Set credentials in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35047,9 +35047,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineCredentials1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineCredentials1 = catparametersCreateDeploymentVirtualMachineCredentials1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineCredentials1 = parametersCreateDeploymentVirtualMachineCredentials1.category('remove') + var removeparametersCreateDeploymentVirtualMachineCredentials1 = parametersCreateDeploymentVirtualMachineCredentials1.category('credentials') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineCredentials1.command('credentials') + removeparametersCreateDeploymentVirtualMachineCredentials1.command('remove') .description($('Remove credentials in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35103,9 +35103,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineCredentials2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineCredentials2 = catparametersCreateDeploymentVirtualMachineCredentials2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineCredentials2 = parametersCreateDeploymentVirtualMachineCredentials2.category('add') + var addparametersCreateDeploymentVirtualMachineCredentials2 = parametersCreateDeploymentVirtualMachineCredentials2.category('credentials') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineCredentials2.command('credentials') + addparametersCreateDeploymentVirtualMachineCredentials2.command('add') .description($('Add credentials in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35177,9 +35177,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineProvisioning0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineProvisioning0 = catparametersCreateDeploymentVirtualMachineProvisioning0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineProvisioning0 = parametersCreateDeploymentVirtualMachineProvisioning0.category('set') + var setparametersCreateDeploymentVirtualMachineProvisioning0 = parametersCreateDeploymentVirtualMachineProvisioning0.category('provisioning') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineProvisioning0.command('provisioning') + setparametersCreateDeploymentVirtualMachineProvisioning0.command('set') .description($('Set provisioning in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35227,9 +35227,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineProvisioning1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineProvisioning1 = catparametersCreateDeploymentVirtualMachineProvisioning1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineProvisioning1 = parametersCreateDeploymentVirtualMachineProvisioning1.category('remove') + var removeparametersCreateDeploymentVirtualMachineProvisioning1 = parametersCreateDeploymentVirtualMachineProvisioning1.category('provisioning') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineProvisioning1.command('provisioning') + removeparametersCreateDeploymentVirtualMachineProvisioning1.command('remove') .description($('Remove provisioning in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35273,9 +35273,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineProvisioning2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineProvisioning2 = catparametersCreateDeploymentVirtualMachineProvisioning2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineProvisioning2 = parametersCreateDeploymentVirtualMachineProvisioning2.category('add') + var addparametersCreateDeploymentVirtualMachineProvisioning2 = parametersCreateDeploymentVirtualMachineProvisioning2.category('provisioning') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineProvisioning2.command('provisioning') + addparametersCreateDeploymentVirtualMachineProvisioning2.command('add') .description($('Add provisioning in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35325,9 +35325,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineInputEndpoints0 = catparametersCreateDeploymentVirtualMachineInputEndpoints0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineInputEndpoints0 = parametersCreateDeploymentVirtualMachineInputEndpoints0.category('set') + var setparametersCreateDeploymentVirtualMachineInputEndpoints0 = parametersCreateDeploymentVirtualMachineInputEndpoints0.category('input-endpoints') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineInputEndpoints0.command('input-endpoints') + setparametersCreateDeploymentVirtualMachineInputEndpoints0.command('set') .description($('Set input-endpoints in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35513,9 +35513,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineInputEndpoints1 = catparametersCreateDeploymentVirtualMachineInputEndpoints1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineInputEndpoints1 = parametersCreateDeploymentVirtualMachineInputEndpoints1.category('remove') + var removeparametersCreateDeploymentVirtualMachineInputEndpoints1 = parametersCreateDeploymentVirtualMachineInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineInputEndpoints1.command('input-endpoints') + removeparametersCreateDeploymentVirtualMachineInputEndpoints1.command('remove') .description($('Remove input-endpoints in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35620,9 +35620,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineInputEndpoints2 = catparametersCreateDeploymentVirtualMachineInputEndpoints2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineInputEndpoints2 = parametersCreateDeploymentVirtualMachineInputEndpoints2.category('add') + var addparametersCreateDeploymentVirtualMachineInputEndpoints2 = parametersCreateDeploymentVirtualMachineInputEndpoints2.category('input-endpoints') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineInputEndpoints2.command('input-endpoints') + addparametersCreateDeploymentVirtualMachineInputEndpoints2.command('add') .description($('Add input-endpoints in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35805,9 +35805,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineEndpointAcl1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineEndpointAcl1 = catparametersCreateDeploymentVirtualMachineEndpointAcl1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineEndpointAcl1 = parametersCreateDeploymentVirtualMachineEndpointAcl1.category('remove') + var removeparametersCreateDeploymentVirtualMachineEndpointAcl1 = parametersCreateDeploymentVirtualMachineEndpointAcl1.category('endpoint-acl') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineEndpointAcl1.command('endpoint-acl') + removeparametersCreateDeploymentVirtualMachineEndpointAcl1.command('remove') .description($('Remove endpoint-acl in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35852,9 +35852,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineEndpointAcl2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineEndpointAcl2 = catparametersCreateDeploymentVirtualMachineEndpointAcl2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineEndpointAcl2 = parametersCreateDeploymentVirtualMachineEndpointAcl2.category('add') + var addparametersCreateDeploymentVirtualMachineEndpointAcl2 = parametersCreateDeploymentVirtualMachineEndpointAcl2.category('endpoint-acl') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineEndpointAcl2.command('endpoint-acl') + addparametersCreateDeploymentVirtualMachineEndpointAcl2.command('add') .description($('Add endpoint-acl in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35904,9 +35904,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRules0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRules0 = catparametersCreateDeploymentVirtualMachineRules0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineRules0 = parametersCreateDeploymentVirtualMachineRules0.category('set') + var setparametersCreateDeploymentVirtualMachineRules0 = parametersCreateDeploymentVirtualMachineRules0.category('rules') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineRules0.command('rules') + setparametersCreateDeploymentVirtualMachineRules0.command('set') .description($('Set rules in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -35993,9 +35993,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRules1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRules1 = catparametersCreateDeploymentVirtualMachineRules1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineRules1 = parametersCreateDeploymentVirtualMachineRules1.category('remove') + var removeparametersCreateDeploymentVirtualMachineRules1 = parametersCreateDeploymentVirtualMachineRules1.category('rules') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineRules1.command('rules') + removeparametersCreateDeploymentVirtualMachineRules1.command('remove') .description($('Remove rules in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36056,9 +36056,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineRules2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineRules2 = catparametersCreateDeploymentVirtualMachineRules2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineRules2 = parametersCreateDeploymentVirtualMachineRules2.category('add') + var addparametersCreateDeploymentVirtualMachineRules2 = parametersCreateDeploymentVirtualMachineRules2.category('rules') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineRules2.command('rules') + addparametersCreateDeploymentVirtualMachineRules2.command('add') .description($('Add rules in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36141,9 +36141,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancerProbe0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancerProbe0 = catparametersCreateDeploymentVirtualMachineLoadBalancerProbe0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineLoadBalancerProbe0 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe0.category('set') + var setparametersCreateDeploymentVirtualMachineLoadBalancerProbe0 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe0.category('load-balancer-probe') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineLoadBalancerProbe0.command('load-balancer-probe') + setparametersCreateDeploymentVirtualMachineLoadBalancerProbe0.command('set') .description($('Set load-balancer-probe in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36236,9 +36236,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancerProbe1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancerProbe1 = catparametersCreateDeploymentVirtualMachineLoadBalancerProbe1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineLoadBalancerProbe1 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe1.category('remove') + var removeparametersCreateDeploymentVirtualMachineLoadBalancerProbe1 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe1.category('load-balancer-probe') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineLoadBalancerProbe1.command('load-balancer-probe') + removeparametersCreateDeploymentVirtualMachineLoadBalancerProbe1.command('remove') .description($('Remove load-balancer-probe in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36303,9 +36303,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineLoadBalancerProbe2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineLoadBalancerProbe2 = catparametersCreateDeploymentVirtualMachineLoadBalancerProbe2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineLoadBalancerProbe2 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe2.category('add') + var addparametersCreateDeploymentVirtualMachineLoadBalancerProbe2 = parametersCreateDeploymentVirtualMachineLoadBalancerProbe2.category('load-balancer-probe') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineLoadBalancerProbe2.command('load-balancer-probe') + addparametersCreateDeploymentVirtualMachineLoadBalancerProbe2.command('add') .description($('Add load-balancer-probe in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36399,9 +36399,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineProtocol1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineProtocol1 = catparametersCreateDeploymentVirtualMachineProtocol1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineProtocol1 = parametersCreateDeploymentVirtualMachineProtocol1.category('remove') + var removeparametersCreateDeploymentVirtualMachineProtocol1 = parametersCreateDeploymentVirtualMachineProtocol1.category('protocol') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineProtocol1.command('protocol') + removeparametersCreateDeploymentVirtualMachineProtocol1.command('remove') .description($('Remove protocol in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36435,9 +36435,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineProtocol2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineProtocol2 = catparametersCreateDeploymentVirtualMachineProtocol2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineProtocol2 = parametersCreateDeploymentVirtualMachineProtocol2.category('add') + var addparametersCreateDeploymentVirtualMachineProtocol2 = parametersCreateDeploymentVirtualMachineProtocol2.category('protocol') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineProtocol2.command('protocol') + addparametersCreateDeploymentVirtualMachineProtocol2.command('add') .description($('Add protocol in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36476,9 +36476,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineNetworkInterfaces0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineNetworkInterfaces0 = catparametersCreateDeploymentVirtualMachineNetworkInterfaces0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineNetworkInterfaces0 = parametersCreateDeploymentVirtualMachineNetworkInterfaces0.category('set') + var setparametersCreateDeploymentVirtualMachineNetworkInterfaces0 = parametersCreateDeploymentVirtualMachineNetworkInterfaces0.category('network-interfaces') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineNetworkInterfaces0.command('network-interfaces') + setparametersCreateDeploymentVirtualMachineNetworkInterfaces0.command('set') .description($('Set network-interfaces in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36564,9 +36564,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineNetworkInterfaces1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineNetworkInterfaces1 = catparametersCreateDeploymentVirtualMachineNetworkInterfaces1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineNetworkInterfaces1 = parametersCreateDeploymentVirtualMachineNetworkInterfaces1.category('remove') + var removeparametersCreateDeploymentVirtualMachineNetworkInterfaces1 = parametersCreateDeploymentVirtualMachineNetworkInterfaces1.category('network-interfaces') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineNetworkInterfaces1.command('network-interfaces') + removeparametersCreateDeploymentVirtualMachineNetworkInterfaces1.command('remove') .description($('Remove network-interfaces in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36626,9 +36626,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineNetworkInterfaces2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineNetworkInterfaces2 = catparametersCreateDeploymentVirtualMachineNetworkInterfaces2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineNetworkInterfaces2 = parametersCreateDeploymentVirtualMachineNetworkInterfaces2.category('add') + var addparametersCreateDeploymentVirtualMachineNetworkInterfaces2 = parametersCreateDeploymentVirtualMachineNetworkInterfaces2.category('network-interfaces') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineNetworkInterfaces2.command('network-interfaces') + addparametersCreateDeploymentVirtualMachineNetworkInterfaces2.command('add') .description($('Add network-interfaces in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36711,9 +36711,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineIPConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineIPConfigurations0 = catparametersCreateDeploymentVirtualMachineIPConfigurations0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineIPConfigurations0 = parametersCreateDeploymentVirtualMachineIPConfigurations0.category('set') + var setparametersCreateDeploymentVirtualMachineIPConfigurations0 = parametersCreateDeploymentVirtualMachineIPConfigurations0.category('ip-configurations') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineIPConfigurations0.command('ip-configurations') + setparametersCreateDeploymentVirtualMachineIPConfigurations0.command('set') .description($('Set ip-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36778,9 +36778,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineIPConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineIPConfigurations1 = catparametersCreateDeploymentVirtualMachineIPConfigurations1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineIPConfigurations1 = parametersCreateDeploymentVirtualMachineIPConfigurations1.category('remove') + var removeparametersCreateDeploymentVirtualMachineIPConfigurations1 = parametersCreateDeploymentVirtualMachineIPConfigurations1.category('ip-configurations') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineIPConfigurations1.command('ip-configurations') + removeparametersCreateDeploymentVirtualMachineIPConfigurations1.command('remove') .description($('Remove ip-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36831,9 +36831,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineIPConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineIPConfigurations2 = catparametersCreateDeploymentVirtualMachineIPConfigurations2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineIPConfigurations2 = parametersCreateDeploymentVirtualMachineIPConfigurations2.category('add') + var addparametersCreateDeploymentVirtualMachineIPConfigurations2 = parametersCreateDeploymentVirtualMachineIPConfigurations2.category('ip-configurations') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineIPConfigurations2.command('ip-configurations') + addparametersCreateDeploymentVirtualMachineIPConfigurations2.command('add') .description($('Add ip-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36894,9 +36894,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicIPs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicIPs0 = catparametersCreateDeploymentVirtualMachinePublicIPs0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachinePublicIPs0 = parametersCreateDeploymentVirtualMachinePublicIPs0.category('set') + var setparametersCreateDeploymentVirtualMachinePublicIPs0 = parametersCreateDeploymentVirtualMachinePublicIPs0.category('public-ip') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachinePublicIPs0.command('public-ip') + setparametersCreateDeploymentVirtualMachinePublicIPs0.command('set') .description($('Set public-ip in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -36971,9 +36971,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicIPs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicIPs1 = catparametersCreateDeploymentVirtualMachinePublicIPs1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachinePublicIPs1 = parametersCreateDeploymentVirtualMachinePublicIPs1.category('remove') + var removeparametersCreateDeploymentVirtualMachinePublicIPs1 = parametersCreateDeploymentVirtualMachinePublicIPs1.category('public-ip') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachinePublicIPs1.command('public-ip') + removeparametersCreateDeploymentVirtualMachinePublicIPs1.command('remove') .description($('Remove public-ip in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37028,9 +37028,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicIPs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicIPs2 = catparametersCreateDeploymentVirtualMachinePublicIPs2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachinePublicIPs2 = parametersCreateDeploymentVirtualMachinePublicIPs2.category('add') + var addparametersCreateDeploymentVirtualMachinePublicIPs2 = parametersCreateDeploymentVirtualMachinePublicIPs2.category('public-ip') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachinePublicIPs2.command('public-ip') + addparametersCreateDeploymentVirtualMachinePublicIPs2.command('add') .description($('Add public-ip in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37102,9 +37102,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineSshSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineSshSettings1 = catparametersCreateDeploymentVirtualMachineSshSettings1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineSshSettings1 = parametersCreateDeploymentVirtualMachineSshSettings1.category('remove') + var removeparametersCreateDeploymentVirtualMachineSshSettings1 = parametersCreateDeploymentVirtualMachineSshSettings1.category('ssh-settings') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineSshSettings1.command('ssh-settings') + removeparametersCreateDeploymentVirtualMachineSshSettings1.command('remove') .description($('Remove ssh-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37153,9 +37153,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineSshSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineSshSettings2 = catparametersCreateDeploymentVirtualMachineSshSettings2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineSshSettings2 = parametersCreateDeploymentVirtualMachineSshSettings2.category('add') + var addparametersCreateDeploymentVirtualMachineSshSettings2 = parametersCreateDeploymentVirtualMachineSshSettings2.category('ssh-settings') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineSshSettings2.command('ssh-settings') + addparametersCreateDeploymentVirtualMachineSshSettings2.command('add') .description($('Add ssh-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37216,9 +37216,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineKeyPairs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineKeyPairs0 = catparametersCreateDeploymentVirtualMachineKeyPairs0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineKeyPairs0 = parametersCreateDeploymentVirtualMachineKeyPairs0.category('set') + var setparametersCreateDeploymentVirtualMachineKeyPairs0 = parametersCreateDeploymentVirtualMachineKeyPairs0.category('key-pairs') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineKeyPairs0.command('key-pairs') + setparametersCreateDeploymentVirtualMachineKeyPairs0.command('set') .description($('Set key-pairs in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37282,9 +37282,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineKeyPairs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineKeyPairs1 = catparametersCreateDeploymentVirtualMachineKeyPairs1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineKeyPairs1 = parametersCreateDeploymentVirtualMachineKeyPairs1.category('remove') + var removeparametersCreateDeploymentVirtualMachineKeyPairs1 = parametersCreateDeploymentVirtualMachineKeyPairs1.category('key-pairs') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineKeyPairs1.command('key-pairs') + removeparametersCreateDeploymentVirtualMachineKeyPairs1.command('remove') .description($('Remove key-pairs in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37334,9 +37334,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineKeyPairs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineKeyPairs2 = catparametersCreateDeploymentVirtualMachineKeyPairs2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineKeyPairs2 = parametersCreateDeploymentVirtualMachineKeyPairs2.category('add') + var addparametersCreateDeploymentVirtualMachineKeyPairs2 = parametersCreateDeploymentVirtualMachineKeyPairs2.category('key-pairs') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineKeyPairs2.command('key-pairs') + addparametersCreateDeploymentVirtualMachineKeyPairs2.command('add') .description($('Add key-pairs in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37397,9 +37397,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicKeys0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicKeys0 = catparametersCreateDeploymentVirtualMachinePublicKeys0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachinePublicKeys0 = parametersCreateDeploymentVirtualMachinePublicKeys0.category('set') + var setparametersCreateDeploymentVirtualMachinePublicKeys0 = parametersCreateDeploymentVirtualMachinePublicKeys0.category('public-keys') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachinePublicKeys0.command('public-keys') + setparametersCreateDeploymentVirtualMachinePublicKeys0.command('set') .description($('Set public-keys in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37463,9 +37463,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicKeys1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicKeys1 = catparametersCreateDeploymentVirtualMachinePublicKeys1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachinePublicKeys1 = parametersCreateDeploymentVirtualMachinePublicKeys1.category('remove') + var removeparametersCreateDeploymentVirtualMachinePublicKeys1 = parametersCreateDeploymentVirtualMachinePublicKeys1.category('public-keys') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachinePublicKeys1.command('public-keys') + removeparametersCreateDeploymentVirtualMachinePublicKeys1.command('remove') .description($('Remove public-keys in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37515,9 +37515,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachinePublicKeys2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachinePublicKeys2 = catparametersCreateDeploymentVirtualMachinePublicKeys2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachinePublicKeys2 = parametersCreateDeploymentVirtualMachinePublicKeys2.category('add') + var addparametersCreateDeploymentVirtualMachinePublicKeys2 = parametersCreateDeploymentVirtualMachinePublicKeys2.category('public-keys') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachinePublicKeys2.command('public-keys') + addparametersCreateDeploymentVirtualMachinePublicKeys2.command('add') .description($('Add public-keys in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37578,9 +37578,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineStoredCertificateSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineStoredCertificateSettings0 = catparametersCreateDeploymentVirtualMachineStoredCertificateSettings0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineStoredCertificateSettings0 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings0.category('set') + var setparametersCreateDeploymentVirtualMachineStoredCertificateSettings0 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings0.category('stored-certificate-settings') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineStoredCertificateSettings0.command('stored-certificate-settings') + setparametersCreateDeploymentVirtualMachineStoredCertificateSettings0.command('set') .description($('Set stored-certificate-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37644,9 +37644,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineStoredCertificateSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineStoredCertificateSettings1 = catparametersCreateDeploymentVirtualMachineStoredCertificateSettings1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineStoredCertificateSettings1 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings1.category('remove') + var removeparametersCreateDeploymentVirtualMachineStoredCertificateSettings1 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings1.category('stored-certificate-settings') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineStoredCertificateSettings1.command('stored-certificate-settings') + removeparametersCreateDeploymentVirtualMachineStoredCertificateSettings1.command('remove') .description($('Remove stored-certificate-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37696,9 +37696,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineStoredCertificateSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineStoredCertificateSettings2 = catparametersCreateDeploymentVirtualMachineStoredCertificateSettings2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineStoredCertificateSettings2 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings2.category('add') + var addparametersCreateDeploymentVirtualMachineStoredCertificateSettings2 = parametersCreateDeploymentVirtualMachineStoredCertificateSettings2.category('stored-certificate-settings') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineStoredCertificateSettings2.command('stored-certificate-settings') + addparametersCreateDeploymentVirtualMachineStoredCertificateSettings2.command('add') .description($('Add stored-certificate-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37759,9 +37759,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineSubnetNames0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineSubnetNames0 = catparametersCreateDeploymentVirtualMachineSubnetNames0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineSubnetNames0 = parametersCreateDeploymentVirtualMachineSubnetNames0.category('set') + var setparametersCreateDeploymentVirtualMachineSubnetNames0 = parametersCreateDeploymentVirtualMachineSubnetNames0.category('subnet-names') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineSubnetNames0.command('subnet-names') + setparametersCreateDeploymentVirtualMachineSubnetNames0.command('set') .description($('Set subnet-names in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37803,9 +37803,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineSubnetNames1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineSubnetNames1 = catparametersCreateDeploymentVirtualMachineSubnetNames1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineSubnetNames1 = parametersCreateDeploymentVirtualMachineSubnetNames1.category('remove') + var removeparametersCreateDeploymentVirtualMachineSubnetNames1 = parametersCreateDeploymentVirtualMachineSubnetNames1.category('subnet-names') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineSubnetNames1.command('subnet-names') + removeparametersCreateDeploymentVirtualMachineSubnetNames1.command('remove') .description($('Remove subnet-names in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37839,9 +37839,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineSubnetNames2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineSubnetNames2 = catparametersCreateDeploymentVirtualMachineSubnetNames2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineSubnetNames2 = parametersCreateDeploymentVirtualMachineSubnetNames2.category('add') + var addparametersCreateDeploymentVirtualMachineSubnetNames2 = parametersCreateDeploymentVirtualMachineSubnetNames2.category('subnet-names') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineSubnetNames2.command('subnet-names') + addparametersCreateDeploymentVirtualMachineSubnetNames2.command('add') .description($('Add subnet-names in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37880,9 +37880,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineWindowsRemoteManagement1 = catparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1 = parametersCreateDeploymentVirtualMachineWindowsRemoteManagement1.category('remove') + var removeparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1 = parametersCreateDeploymentVirtualMachineWindowsRemoteManagement1.category('windows-remote-management') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1.command('windows-remote-management') + removeparametersCreateDeploymentVirtualMachineWindowsRemoteManagement1.command('remove') .description($('Remove windows-remote-management in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37926,9 +37926,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineWindowsRemoteManagement2 = catparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2 = parametersCreateDeploymentVirtualMachineWindowsRemoteManagement2.category('add') + var addparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2 = parametersCreateDeploymentVirtualMachineWindowsRemoteManagement2.category('windows-remote-management') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2.command('windows-remote-management') + addparametersCreateDeploymentVirtualMachineWindowsRemoteManagement2.command('add') .description($('Add windows-remote-management in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -37978,9 +37978,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineListeners0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineListeners0 = catparametersCreateDeploymentVirtualMachineListeners0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineListeners0 = parametersCreateDeploymentVirtualMachineListeners0.category('set') + var setparametersCreateDeploymentVirtualMachineListeners0 = parametersCreateDeploymentVirtualMachineListeners0.category('listeners') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineListeners0.command('listeners') + setparametersCreateDeploymentVirtualMachineListeners0.command('set') .description($('Set listeners in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38044,9 +38044,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineListeners1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineListeners1 = catparametersCreateDeploymentVirtualMachineListeners1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineListeners1 = parametersCreateDeploymentVirtualMachineListeners1.category('remove') + var removeparametersCreateDeploymentVirtualMachineListeners1 = parametersCreateDeploymentVirtualMachineListeners1.category('listeners') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineListeners1.command('listeners') + removeparametersCreateDeploymentVirtualMachineListeners1.command('remove') .description($('Remove listeners in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38096,9 +38096,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineListeners2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineListeners2 = catparametersCreateDeploymentVirtualMachineListeners2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineListeners2 = parametersCreateDeploymentVirtualMachineListeners2.category('add') + var addparametersCreateDeploymentVirtualMachineListeners2 = parametersCreateDeploymentVirtualMachineListeners2.category('listeners') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineListeners2.command('listeners') + addparametersCreateDeploymentVirtualMachineListeners2.command('add') .description($('Add listeners in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38159,9 +38159,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineListenerType1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineListenerType1 = catparametersCreateDeploymentVirtualMachineListenerType1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineListenerType1 = parametersCreateDeploymentVirtualMachineListenerType1.category('remove') + var removeparametersCreateDeploymentVirtualMachineListenerType1 = parametersCreateDeploymentVirtualMachineListenerType1.category('listener-type') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineListenerType1.command('listener-type') + removeparametersCreateDeploymentVirtualMachineListenerType1.command('remove') .description($('Remove listener-type in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38195,9 +38195,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineListenerType2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineListenerType2 = catparametersCreateDeploymentVirtualMachineListenerType2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineListenerType2 = parametersCreateDeploymentVirtualMachineListenerType2.category('add') + var addparametersCreateDeploymentVirtualMachineListenerType2 = parametersCreateDeploymentVirtualMachineListenerType2.category('listener-type') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineListenerType2.command('listener-type') + addparametersCreateDeploymentVirtualMachineListenerType2.command('add') .description($('Add listener-type in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38236,9 +38236,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataVirtualHardDisks0 = catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks0.category('set') + var setparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks0.category('data-virtual-hard-disks') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0.command('data-virtual-hard-disks') + setparametersCreateDeploymentVirtualMachineDataVirtualHardDisks0.command('set') .description($('Set data-virtual-hard-disks in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38367,9 +38367,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataVirtualHardDisks1 = catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks1.category('data-virtual-hard-disks') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1.command('data-virtual-hard-disks') + removeparametersCreateDeploymentVirtualMachineDataVirtualHardDisks1.command('remove') .description($('Remove data-virtual-hard-disks in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38448,9 +38448,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataVirtualHardDisks2 = catparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks2.category('add') + var addparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2 = parametersCreateDeploymentVirtualMachineDataVirtualHardDisks2.category('data-virtual-hard-disks') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2.command('data-virtual-hard-disks') + addparametersCreateDeploymentVirtualMachineDataVirtualHardDisks2.command('add') .description($('Add data-virtual-hard-disks in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38577,9 +38577,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDebugSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDebugSettings0 = catparametersCreateDeploymentVirtualMachineDebugSettings0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineDebugSettings0 = parametersCreateDeploymentVirtualMachineDebugSettings0.category('set') + var setparametersCreateDeploymentVirtualMachineDebugSettings0 = parametersCreateDeploymentVirtualMachineDebugSettings0.category('debug-settings') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineDebugSettings0.command('debug-settings') + setparametersCreateDeploymentVirtualMachineDebugSettings0.command('set') .description($('Set debug-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38648,9 +38648,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDebugSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDebugSettings1 = catparametersCreateDeploymentVirtualMachineDebugSettings1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDebugSettings1 = parametersCreateDeploymentVirtualMachineDebugSettings1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDebugSettings1 = parametersCreateDeploymentVirtualMachineDebugSettings1.category('debug-settings') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDebugSettings1.command('debug-settings') + removeparametersCreateDeploymentVirtualMachineDebugSettings1.command('remove') .description($('Remove debug-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38703,9 +38703,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDebugSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDebugSettings2 = catparametersCreateDeploymentVirtualMachineDebugSettings2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDebugSettings2 = parametersCreateDeploymentVirtualMachineDebugSettings2.category('add') + var addparametersCreateDeploymentVirtualMachineDebugSettings2 = parametersCreateDeploymentVirtualMachineDebugSettings2.category('debug-settings') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDebugSettings2.command('debug-settings') + addparametersCreateDeploymentVirtualMachineDebugSettings2.command('add') .description($('Add debug-settings in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38777,9 +38777,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSVirtualHardDisk0 = catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk0.category('set') + var setparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk0.category('os-virtual-hard-disk') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0.command('os-virtual-hard-disk') + setparametersCreateDeploymentVirtualMachineOSVirtualHardDisk0.command('set') .description($('Set os-virtual-hard-disk in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38914,9 +38914,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSVirtualHardDisk1 = catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk1.category('remove') + var removeparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk1.category('os-virtual-hard-disk') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1.command('os-virtual-hard-disk') + removeparametersCreateDeploymentVirtualMachineOSVirtualHardDisk1.command('remove') .description($('Remove os-virtual-hard-disk in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -38999,9 +38999,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSVirtualHardDisk2 = catparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk2.category('add') + var addparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2 = parametersCreateDeploymentVirtualMachineOSVirtualHardDisk2.category('os-virtual-hard-disk') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2.command('os-virtual-hard-disk') + addparametersCreateDeploymentVirtualMachineOSVirtualHardDisk2.command('add') .description($('Add os-virtual-hard-disk in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39139,9 +39139,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionReferences0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionReferences0 = catparametersCreateDeploymentVirtualMachineResourceExtensionReferences0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineResourceExtensionReferences0 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences0.category('set') + var setparametersCreateDeploymentVirtualMachineResourceExtensionReferences0 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences0.category('resource-extension-references') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineResourceExtensionReferences0.command('resource-extension-references') + setparametersCreateDeploymentVirtualMachineResourceExtensionReferences0.command('set') .description($('Set resource-extension-references in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39260,9 +39260,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionReferences1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionReferences1 = catparametersCreateDeploymentVirtualMachineResourceExtensionReferences1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineResourceExtensionReferences1 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences1.category('remove') + var removeparametersCreateDeploymentVirtualMachineResourceExtensionReferences1 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences1.category('resource-extension-references') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineResourceExtensionReferences1.command('resource-extension-references') + removeparametersCreateDeploymentVirtualMachineResourceExtensionReferences1.command('remove') .description($('Remove resource-extension-references in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39336,9 +39336,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionReferences2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionReferences2 = catparametersCreateDeploymentVirtualMachineResourceExtensionReferences2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineResourceExtensionReferences2 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences2.category('add') + var addparametersCreateDeploymentVirtualMachineResourceExtensionReferences2 = parametersCreateDeploymentVirtualMachineResourceExtensionReferences2.category('resource-extension-references') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineResourceExtensionReferences2.command('resource-extension-references') + addparametersCreateDeploymentVirtualMachineResourceExtensionReferences2.command('add') .description($('Add resource-extension-references in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39455,9 +39455,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0 = catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0.category('set') + var setparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0.category('resource-extension-parameter-values') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0.command('resource-extension-parameter-values') + setparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues0.command('set') .description($('Set resource-extension-parameter-values in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39532,9 +39532,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1 = catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1.category('remove') + var removeparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1.category('resource-extension-parameter-values') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1.command('resource-extension-parameter-values') + removeparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues1.command('remove') .description($('Remove resource-extension-parameter-values in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39589,9 +39589,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2 = catparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2.category('add') + var addparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2 = parametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2.category('resource-extension-parameter-values') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2.command('resource-extension-parameter-values') + addparametersCreateDeploymentVirtualMachineResourceExtensionParameterValues2.command('add') .description($('Add resource-extension-parameter-values in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39663,9 +39663,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineVMImageInput1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineVMImageInput1 = catparametersCreateDeploymentVirtualMachineVMImageInput1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineVMImageInput1 = parametersCreateDeploymentVirtualMachineVMImageInput1.category('remove') + var removeparametersCreateDeploymentVirtualMachineVMImageInput1 = parametersCreateDeploymentVirtualMachineVMImageInput1.category('vm-image-input') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineVMImageInput1.command('vm-image-input') + removeparametersCreateDeploymentVirtualMachineVMImageInput1.command('remove') .description($('Remove vm-image-input in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "vMImageInput" : {\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39713,9 +39713,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineVMImageInput2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineVMImageInput2 = catparametersCreateDeploymentVirtualMachineVMImageInput2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineVMImageInput2 = parametersCreateDeploymentVirtualMachineVMImageInput2.category('add') + var addparametersCreateDeploymentVirtualMachineVMImageInput2 = parametersCreateDeploymentVirtualMachineVMImageInput2.category('vm-image-input') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineVMImageInput2.command('vm-image-input') + addparametersCreateDeploymentVirtualMachineVMImageInput2.command('add') .description($('Add vm-image-input in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "vMImageInput" : {\r\n "dataDiskConfigurations":[\r\n {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ],\r\n "oSDiskConfiguration":{\r\n "resizedSizeInGB":null\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39776,9 +39776,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataDiskConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataDiskConfigurations0 = catparametersCreateDeploymentVirtualMachineDataDiskConfigurations0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineDataDiskConfigurations0 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations0.category('set') + var setparametersCreateDeploymentVirtualMachineDataDiskConfigurations0 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations0.category('data-disk-configurations') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineDataDiskConfigurations0.command('data-disk-configurations') + setparametersCreateDeploymentVirtualMachineDataDiskConfigurations0.command('set') .description($('Set data-disk-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39841,9 +39841,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataDiskConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataDiskConfigurations1 = catparametersCreateDeploymentVirtualMachineDataDiskConfigurations1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineDataDiskConfigurations1 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations1.category('remove') + var removeparametersCreateDeploymentVirtualMachineDataDiskConfigurations1 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations1.category('data-disk-configurations') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineDataDiskConfigurations1.command('data-disk-configurations') + removeparametersCreateDeploymentVirtualMachineDataDiskConfigurations1.command('remove') .description($('Remove data-disk-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39892,9 +39892,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineDataDiskConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineDataDiskConfigurations2 = catparametersCreateDeploymentVirtualMachineDataDiskConfigurations2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineDataDiskConfigurations2 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations2.category('add') + var addparametersCreateDeploymentVirtualMachineDataDiskConfigurations2 = parametersCreateDeploymentVirtualMachineDataDiskConfigurations2.category('data-disk-configurations') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineDataDiskConfigurations2.command('data-disk-configurations') + addparametersCreateDeploymentVirtualMachineDataDiskConfigurations2.command('add') .description($('Add data-disk-configurations in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "diskName":"",\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -39955,9 +39955,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSDiskConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSDiskConfiguration0 = catparametersCreateDeploymentVirtualMachineOSDiskConfiguration0.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersCreateDeploymentVirtualMachineOSDiskConfiguration0 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration0.category('set') + var setparametersCreateDeploymentVirtualMachineOSDiskConfiguration0 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration0.category('os-disk-configuration') .description($('Commands to set components of virtual-machine in create-deployment-parameters file.')); - setparametersCreateDeploymentVirtualMachineOSDiskConfiguration0.command('os-disk-configuration') + setparametersCreateDeploymentVirtualMachineOSDiskConfiguration0.command('set') .description($('Set os-disk-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40004,9 +40004,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSDiskConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSDiskConfiguration1 = catparametersCreateDeploymentVirtualMachineOSDiskConfiguration1.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersCreateDeploymentVirtualMachineOSDiskConfiguration1 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration1.category('remove') + var removeparametersCreateDeploymentVirtualMachineOSDiskConfiguration1 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration1.category('os-disk-configuration') .description($('Commands to remove components of virtual-machine in create-deployment-parameters file.')); - removeparametersCreateDeploymentVirtualMachineOSDiskConfiguration1.command('os-disk-configuration') + removeparametersCreateDeploymentVirtualMachineOSDiskConfiguration1.command('remove') .description($('Remove os-disk-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40049,9 +40049,9 @@ exports.init = function (cli) { var catparametersCreateDeploymentVirtualMachineOSDiskConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersCreateDeploymentVirtualMachineOSDiskConfiguration2 = catparametersCreateDeploymentVirtualMachineOSDiskConfiguration2.category('create-deployment-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersCreateDeploymentVirtualMachineOSDiskConfiguration2 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration2.category('add') + var addparametersCreateDeploymentVirtualMachineOSDiskConfiguration2 = parametersCreateDeploymentVirtualMachineOSDiskConfiguration2.category('os-disk-configuration') .description($('Commands to add components of virtual-machine in create-deployment-parameters file.')); - addparametersCreateDeploymentVirtualMachineOSDiskConfiguration2.command('os-disk-configuration') + addparametersCreateDeploymentVirtualMachineOSDiskConfiguration2.command('add') .description($('Add os-disk-configuration in create-deployment-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "resizedSizeInGB":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40388,9 +40388,9 @@ exports.init = function (cli) { var catparametersShutdownVirtualMachineVirtualMachineShutdownParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownVirtualMachineVirtualMachineShutdownParameters1 = catparametersShutdownVirtualMachineVirtualMachineShutdownParameters1.category('shutdown-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersShutdownVirtualMachineVirtualMachineShutdownParameters1 = parametersShutdownVirtualMachineVirtualMachineShutdownParameters1.category('remove') + var removeparametersShutdownVirtualMachineVirtualMachineShutdownParameters1 = parametersShutdownVirtualMachineVirtualMachineShutdownParameters1.category('virtual-machine-shutdown-parameters') .description($('Commands to remove components of virtual-machine in shutdown-parameters file.')); - removeparametersShutdownVirtualMachineVirtualMachineShutdownParameters1.command('virtual-machine-shutdown-parameters') + removeparametersShutdownVirtualMachineVirtualMachineShutdownParameters1.command('remove') .description($('Remove virtual-machine-shutdown-parameters in shutdown-parameters string or files, e.g. \r\n{\r\n "postShutdownAction":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40432,9 +40432,9 @@ exports.init = function (cli) { var catparametersShutdownVirtualMachineVirtualMachineShutdownParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownVirtualMachineVirtualMachineShutdownParameters2 = catparametersShutdownVirtualMachineVirtualMachineShutdownParameters2.category('shutdown-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersShutdownVirtualMachineVirtualMachineShutdownParameters2 = parametersShutdownVirtualMachineVirtualMachineShutdownParameters2.category('add') + var addparametersShutdownVirtualMachineVirtualMachineShutdownParameters2 = parametersShutdownVirtualMachineVirtualMachineShutdownParameters2.category('virtual-machine-shutdown-parameters') .description($('Commands to add components of virtual-machine in shutdown-parameters file.')); - addparametersShutdownVirtualMachineVirtualMachineShutdownParameters2.command('virtual-machine-shutdown-parameters') + addparametersShutdownVirtualMachineVirtualMachineShutdownParameters2.command('add') .description($('Add virtual-machine-shutdown-parameters in shutdown-parameters string or files, e.g. \r\n{\r\n "postShutdownAction":0\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40484,9 +40484,9 @@ exports.init = function (cli) { var catparametersShutdownVirtualMachinePostShutdownAction1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownVirtualMachinePostShutdownAction1 = catparametersShutdownVirtualMachinePostShutdownAction1.category('shutdown-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersShutdownVirtualMachinePostShutdownAction1 = parametersShutdownVirtualMachinePostShutdownAction1.category('remove') + var removeparametersShutdownVirtualMachinePostShutdownAction1 = parametersShutdownVirtualMachinePostShutdownAction1.category('post-shutdown-action') .description($('Commands to remove components of virtual-machine in shutdown-parameters file.')); - removeparametersShutdownVirtualMachinePostShutdownAction1.command('post-shutdown-action') + removeparametersShutdownVirtualMachinePostShutdownAction1.command('remove') .description($('Remove post-shutdown-action in shutdown-parameters string or files, e.g. \r\n {\r\n ...\r\n "postShutdownAction" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40516,9 +40516,9 @@ exports.init = function (cli) { var catparametersShutdownVirtualMachinePostShutdownAction2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownVirtualMachinePostShutdownAction2 = catparametersShutdownVirtualMachinePostShutdownAction2.category('shutdown-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersShutdownVirtualMachinePostShutdownAction2 = parametersShutdownVirtualMachinePostShutdownAction2.category('add') + var addparametersShutdownVirtualMachinePostShutdownAction2 = parametersShutdownVirtualMachinePostShutdownAction2.category('post-shutdown-action') .description($('Commands to add components of virtual-machine in shutdown-parameters file.')); - addparametersShutdownVirtualMachinePostShutdownAction2.command('post-shutdown-action') + addparametersShutdownVirtualMachinePostShutdownAction2.command('add') .description($('Add post-shutdown-action in shutdown-parameters string or files, e.g. \r\n {\r\n ...\r\n "postShutdownAction" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40673,9 +40673,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0 = catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0.category('set') + var setparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0.category('virtual-machine-shutdown-roles-parameters') .description($('Commands to set components of virtual-machine in shutdown-roles-parameters file.')); - setparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0.command('virtual-machine-shutdown-roles-parameters') + setparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters0.command('set') .description($('Set virtual-machine-shutdown-roles-parameters in shutdown-roles-parameters string or files, e.g. \r\n{\r\n "postShutdownAction":null,\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40732,9 +40732,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1 = catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1.category('remove') + var removeparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1.category('virtual-machine-shutdown-roles-parameters') .description($('Commands to remove components of virtual-machine in shutdown-roles-parameters file.')); - removeparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1.command('virtual-machine-shutdown-roles-parameters') + removeparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters1.command('remove') .description($('Remove virtual-machine-shutdown-roles-parameters in shutdown-roles-parameters string or files, e.g. \r\n{\r\n "postShutdownAction":null,\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40781,9 +40781,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2 = catparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2.category('add') + var addparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2 = parametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2.category('virtual-machine-shutdown-roles-parameters') .description($('Commands to add components of virtual-machine in shutdown-roles-parameters file.')); - addparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2.command('virtual-machine-shutdown-roles-parameters') + addparametersShutdownRolesVirtualMachineVirtualMachineShutdownRolesParameters2.command('add') .description($('Add virtual-machine-shutdown-roles-parameters in shutdown-roles-parameters string or files, e.g. \r\n{\r\n "postShutdownAction":null,\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40844,9 +40844,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineRoles0 = catparametersShutdownRolesVirtualMachineRoles0.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersShutdownRolesVirtualMachineRoles0 = parametersShutdownRolesVirtualMachineRoles0.category('set') + var setparametersShutdownRolesVirtualMachineRoles0 = parametersShutdownRolesVirtualMachineRoles0.category('roles') .description($('Commands to set components of virtual-machine in shutdown-roles-parameters file.')); - setparametersShutdownRolesVirtualMachineRoles0.command('roles') + setparametersShutdownRolesVirtualMachineRoles0.command('set') .description($('Set roles in shutdown-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40886,9 +40886,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineRoles1 = catparametersShutdownRolesVirtualMachineRoles1.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersShutdownRolesVirtualMachineRoles1 = parametersShutdownRolesVirtualMachineRoles1.category('remove') + var removeparametersShutdownRolesVirtualMachineRoles1 = parametersShutdownRolesVirtualMachineRoles1.category('roles') .description($('Commands to remove components of virtual-machine in shutdown-roles-parameters file.')); - removeparametersShutdownRolesVirtualMachineRoles1.command('roles') + removeparametersShutdownRolesVirtualMachineRoles1.command('remove') .description($('Remove roles in shutdown-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -40920,9 +40920,9 @@ exports.init = function (cli) { var catparametersShutdownRolesVirtualMachineRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersShutdownRolesVirtualMachineRoles2 = catparametersShutdownRolesVirtualMachineRoles2.category('shutdown-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersShutdownRolesVirtualMachineRoles2 = parametersShutdownRolesVirtualMachineRoles2.category('add') + var addparametersShutdownRolesVirtualMachineRoles2 = parametersShutdownRolesVirtualMachineRoles2.category('roles') .description($('Commands to add components of virtual-machine in shutdown-roles-parameters file.')); - addparametersShutdownRolesVirtualMachineRoles2.command('roles') + addparametersShutdownRolesVirtualMachineRoles2.command('add') .description($('Add roles in shutdown-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41120,9 +41120,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0 = catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0.category('set') + var setparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0.category('virtual-machine-start-roles-parameters') .description($('Commands to set components of virtual-machine in start-roles-parameters file.')); - setparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0.command('virtual-machine-start-roles-parameters') + setparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters0.command('set') .description($('Set virtual-machine-start-roles-parameters in start-roles-parameters string or files, e.g. \r\n{\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41168,9 +41168,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1 = catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1.category('remove') + var removeparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1.category('virtual-machine-start-roles-parameters') .description($('Commands to remove components of virtual-machine in start-roles-parameters file.')); - removeparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1.command('virtual-machine-start-roles-parameters') + removeparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters1.command('remove') .description($('Remove virtual-machine-start-roles-parameters in start-roles-parameters string or files, e.g. \r\n{\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41212,9 +41212,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2 = catparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2.category('add') + var addparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2 = parametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2.category('virtual-machine-start-roles-parameters') .description($('Commands to add components of virtual-machine in start-roles-parameters file.')); - addparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2.command('virtual-machine-start-roles-parameters') + addparametersStartRolesVirtualMachineVirtualMachineStartRolesParameters2.command('add') .description($('Add virtual-machine-start-roles-parameters in start-roles-parameters string or files, e.g. \r\n{\r\n "roles":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41264,9 +41264,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineRoles0 = catparametersStartRolesVirtualMachineRoles0.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersStartRolesVirtualMachineRoles0 = parametersStartRolesVirtualMachineRoles0.category('set') + var setparametersStartRolesVirtualMachineRoles0 = parametersStartRolesVirtualMachineRoles0.category('roles') .description($('Commands to set components of virtual-machine in start-roles-parameters file.')); - setparametersStartRolesVirtualMachineRoles0.command('roles') + setparametersStartRolesVirtualMachineRoles0.command('set') .description($('Set roles in start-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41306,9 +41306,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineRoles1 = catparametersStartRolesVirtualMachineRoles1.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersStartRolesVirtualMachineRoles1 = parametersStartRolesVirtualMachineRoles1.category('remove') + var removeparametersStartRolesVirtualMachineRoles1 = parametersStartRolesVirtualMachineRoles1.category('roles') .description($('Commands to remove components of virtual-machine in start-roles-parameters file.')); - removeparametersStartRolesVirtualMachineRoles1.command('roles') + removeparametersStartRolesVirtualMachineRoles1.command('remove') .description($('Remove roles in start-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41340,9 +41340,9 @@ exports.init = function (cli) { var catparametersStartRolesVirtualMachineRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersStartRolesVirtualMachineRoles2 = catparametersStartRolesVirtualMachineRoles2.category('start-roles-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersStartRolesVirtualMachineRoles2 = parametersStartRolesVirtualMachineRoles2.category('add') + var addparametersStartRolesVirtualMachineRoles2 = parametersStartRolesVirtualMachineRoles2.category('roles') .description($('Commands to add components of virtual-machine in start-roles-parameters file.')); - addparametersStartRolesVirtualMachineRoles2.command('roles') + addparametersStartRolesVirtualMachineRoles2.command('add') .description($('Add roles in start-roles-parameters string or files, e.g. \r\n {\r\n ...\r\n "roles" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41682,9 +41682,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVirtualMachineUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineVirtualMachineUpdateParameters0 = catparametersUpdateVirtualMachineVirtualMachineUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineVirtualMachineUpdateParameters0 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters0.category('set') + var setparametersUpdateVirtualMachineVirtualMachineUpdateParameters0 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters0.category('virtual-machine-update-parameters') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineVirtualMachineUpdateParameters0.command('virtual-machine-update-parameters') + setparametersUpdateVirtualMachineVirtualMachineUpdateParameters0.command('set') .description($('Set virtual-machine-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "label":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41830,9 +41830,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVirtualMachineUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineVirtualMachineUpdateParameters1 = catparametersUpdateVirtualMachineVirtualMachineUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineVirtualMachineUpdateParameters1 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters1.category('remove') + var removeparametersUpdateVirtualMachineVirtualMachineUpdateParameters1 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters1.category('virtual-machine-update-parameters') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineVirtualMachineUpdateParameters1.command('virtual-machine-update-parameters') + removeparametersUpdateVirtualMachineVirtualMachineUpdateParameters1.command('remove') .description($('Remove virtual-machine-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "label":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -41919,9 +41919,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVirtualMachineUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineVirtualMachineUpdateParameters2 = catparametersUpdateVirtualMachineVirtualMachineUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineVirtualMachineUpdateParameters2 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters2.category('add') + var addparametersUpdateVirtualMachineVirtualMachineUpdateParameters2 = parametersUpdateVirtualMachineVirtualMachineUpdateParameters2.category('virtual-machine-update-parameters') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineVirtualMachineUpdateParameters2.command('virtual-machine-update-parameters') + addparametersUpdateVirtualMachineVirtualMachineUpdateParameters2.command('add') .description($('Add virtual-machine-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "availabilitySetName":"",\r\n "configurationSets":[\r\n {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ],\r\n "dataVirtualHardDisks":[\r\n {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ],\r\n "debugSettings":{\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n },\r\n "label":"",\r\n "oSVirtualHardDisk":{\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n },\r\n "provisionGuestAgent":null,\r\n "resourceExtensionReferences":[\r\n {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ],\r\n "roleName":"",\r\n "roleSize":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42071,9 +42071,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineConfigurationSets0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineConfigurationSets0 = catparametersUpdateVirtualMachineConfigurationSets0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineConfigurationSets0 = parametersUpdateVirtualMachineConfigurationSets0.category('set') + var setparametersUpdateVirtualMachineConfigurationSets0 = parametersUpdateVirtualMachineConfigurationSets0.category('configuration-sets') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineConfigurationSets0.command('configuration-sets') + setparametersUpdateVirtualMachineConfigurationSets0.command('set') .description($('Set configuration-sets in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42380,9 +42380,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineConfigurationSets1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineConfigurationSets1 = catparametersUpdateVirtualMachineConfigurationSets1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineConfigurationSets1 = parametersUpdateVirtualMachineConfigurationSets1.category('remove') + var removeparametersUpdateVirtualMachineConfigurationSets1 = parametersUpdateVirtualMachineConfigurationSets1.category('configuration-sets') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineConfigurationSets1.command('configuration-sets') + removeparametersUpdateVirtualMachineConfigurationSets1.command('remove') .description($('Remove configuration-sets in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42540,9 +42540,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineConfigurationSets2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineConfigurationSets2 = catparametersUpdateVirtualMachineConfigurationSets2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineConfigurationSets2 = parametersUpdateVirtualMachineConfigurationSets2.category('add') + var addparametersUpdateVirtualMachineConfigurationSets2 = parametersUpdateVirtualMachineConfigurationSets2.category('configuration-sets') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineConfigurationSets2.command('configuration-sets') + addparametersUpdateVirtualMachineConfigurationSets2.command('add') .description($('Add configuration-sets in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "configurationSets" : {\r\n "additionalUnattendContent":{\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n },\r\n "adminPassword":"",\r\n "adminUserName":"",\r\n "computerName":"",\r\n "configurationSetType":"",\r\n "customData":"",\r\n "disableSshPasswordAuthentication":null,\r\n "domainJoin":{\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n },\r\n "enableAutomaticUpdates":null,\r\n "hostName":"",\r\n "inputEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "networkInterfaces":[\r\n {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ],\r\n "networkSecurityGroup":"",\r\n "publicIPs":[\r\n {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ],\r\n "resetPasswordOnFirstLogon":null,\r\n "sshSettings":{\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n },\r\n "staticVirtualNetworkIPAddress":"",\r\n "storedCertificateSettings":[\r\n {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ],\r\n "subnetNames":[\r\n ""\r\n ],\r\n "timeZone":"",\r\n "userName":"",\r\n "userPassword":"",\r\n "windowsRemoteManagement":{\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42848,9 +42848,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineAdditionalUnattendContent1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineAdditionalUnattendContent1 = catparametersUpdateVirtualMachineAdditionalUnattendContent1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineAdditionalUnattendContent1 = parametersUpdateVirtualMachineAdditionalUnattendContent1.category('remove') + var removeparametersUpdateVirtualMachineAdditionalUnattendContent1 = parametersUpdateVirtualMachineAdditionalUnattendContent1.category('additional-unattend-content') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineAdditionalUnattendContent1.command('additional-unattend-content') + removeparametersUpdateVirtualMachineAdditionalUnattendContent1.command('remove') .description($('Remove additional-unattend-content in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42893,9 +42893,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineAdditionalUnattendContent2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineAdditionalUnattendContent2 = catparametersUpdateVirtualMachineAdditionalUnattendContent2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineAdditionalUnattendContent2 = parametersUpdateVirtualMachineAdditionalUnattendContent2.category('add') + var addparametersUpdateVirtualMachineAdditionalUnattendContent2 = parametersUpdateVirtualMachineAdditionalUnattendContent2.category('additional-unattend-content') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineAdditionalUnattendContent2.command('additional-unattend-content') + addparametersUpdateVirtualMachineAdditionalUnattendContent2.command('add') .description($('Add additional-unattend-content in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "additionalUnattendContent" : {\r\n "unattendPasses":[\r\n {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -42945,9 +42945,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendPasses0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendPasses0 = catparametersUpdateVirtualMachineUnattendPasses0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineUnattendPasses0 = parametersUpdateVirtualMachineUnattendPasses0.category('set') + var setparametersUpdateVirtualMachineUnattendPasses0 = parametersUpdateVirtualMachineUnattendPasses0.category('unattend-passes') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineUnattendPasses0.command('unattend-passes') + setparametersUpdateVirtualMachineUnattendPasses0.command('set') .description($('Set unattend-passes in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43010,9 +43010,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendPasses1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendPasses1 = catparametersUpdateVirtualMachineUnattendPasses1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineUnattendPasses1 = parametersUpdateVirtualMachineUnattendPasses1.category('remove') + var removeparametersUpdateVirtualMachineUnattendPasses1 = parametersUpdateVirtualMachineUnattendPasses1.category('unattend-passes') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineUnattendPasses1.command('unattend-passes') + removeparametersUpdateVirtualMachineUnattendPasses1.command('remove') .description($('Remove unattend-passes in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43061,9 +43061,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendPasses2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendPasses2 = catparametersUpdateVirtualMachineUnattendPasses2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineUnattendPasses2 = parametersUpdateVirtualMachineUnattendPasses2.category('add') + var addparametersUpdateVirtualMachineUnattendPasses2 = parametersUpdateVirtualMachineUnattendPasses2.category('unattend-passes') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineUnattendPasses2.command('unattend-passes') + addparametersUpdateVirtualMachineUnattendPasses2.command('add') .description($('Add unattend-passes in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendPasses" : {\r\n "passName":"",\r\n "unattendComponents":[\r\n {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43124,9 +43124,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponents0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponents0 = catparametersUpdateVirtualMachineUnattendComponents0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineUnattendComponents0 = parametersUpdateVirtualMachineUnattendComponents0.category('set') + var setparametersUpdateVirtualMachineUnattendComponents0 = parametersUpdateVirtualMachineUnattendComponents0.category('unattend-components') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineUnattendComponents0.command('unattend-components') + setparametersUpdateVirtualMachineUnattendComponents0.command('set') .description($('Set unattend-components in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43190,9 +43190,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponents1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponents1 = catparametersUpdateVirtualMachineUnattendComponents1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineUnattendComponents1 = parametersUpdateVirtualMachineUnattendComponents1.category('remove') + var removeparametersUpdateVirtualMachineUnattendComponents1 = parametersUpdateVirtualMachineUnattendComponents1.category('unattend-components') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineUnattendComponents1.command('unattend-components') + removeparametersUpdateVirtualMachineUnattendComponents1.command('remove') .description($('Remove unattend-components in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43242,9 +43242,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponents2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponents2 = catparametersUpdateVirtualMachineUnattendComponents2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineUnattendComponents2 = parametersUpdateVirtualMachineUnattendComponents2.category('add') + var addparametersUpdateVirtualMachineUnattendComponents2 = parametersUpdateVirtualMachineUnattendComponents2.category('unattend-components') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineUnattendComponents2.command('unattend-components') + addparametersUpdateVirtualMachineUnattendComponents2.command('add') .description($('Add unattend-components in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponents" : {\r\n "componentName":"",\r\n "unattendComponentSettings":[\r\n {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43305,9 +43305,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponentSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponentSettings0 = catparametersUpdateVirtualMachineUnattendComponentSettings0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineUnattendComponentSettings0 = parametersUpdateVirtualMachineUnattendComponentSettings0.category('set') + var setparametersUpdateVirtualMachineUnattendComponentSettings0 = parametersUpdateVirtualMachineUnattendComponentSettings0.category('unattend-component-settings') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineUnattendComponentSettings0.command('unattend-component-settings') + setparametersUpdateVirtualMachineUnattendComponentSettings0.command('set') .description($('Set unattend-component-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43372,9 +43372,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponentSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponentSettings1 = catparametersUpdateVirtualMachineUnattendComponentSettings1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineUnattendComponentSettings1 = parametersUpdateVirtualMachineUnattendComponentSettings1.category('remove') + var removeparametersUpdateVirtualMachineUnattendComponentSettings1 = parametersUpdateVirtualMachineUnattendComponentSettings1.category('unattend-component-settings') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineUnattendComponentSettings1.command('unattend-component-settings') + removeparametersUpdateVirtualMachineUnattendComponentSettings1.command('remove') .description($('Remove unattend-component-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43425,9 +43425,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineUnattendComponentSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineUnattendComponentSettings2 = catparametersUpdateVirtualMachineUnattendComponentSettings2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineUnattendComponentSettings2 = parametersUpdateVirtualMachineUnattendComponentSettings2.category('add') + var addparametersUpdateVirtualMachineUnattendComponentSettings2 = parametersUpdateVirtualMachineUnattendComponentSettings2.category('unattend-component-settings') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineUnattendComponentSettings2.command('unattend-component-settings') + addparametersUpdateVirtualMachineUnattendComponentSettings2.command('add') .description($('Add unattend-component-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "unattendComponentSettings" : {\r\n "content":"",\r\n "settingName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43488,9 +43488,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDomainJoin0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDomainJoin0 = catparametersUpdateVirtualMachineDomainJoin0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineDomainJoin0 = parametersUpdateVirtualMachineDomainJoin0.category('set') + var setparametersUpdateVirtualMachineDomainJoin0 = parametersUpdateVirtualMachineDomainJoin0.category('domain-join') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineDomainJoin0.command('domain-join') + setparametersUpdateVirtualMachineDomainJoin0.command('set') .description($('Set domain-join in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43570,9 +43570,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDomainJoin1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDomainJoin1 = catparametersUpdateVirtualMachineDomainJoin1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineDomainJoin1 = parametersUpdateVirtualMachineDomainJoin1.category('remove') + var removeparametersUpdateVirtualMachineDomainJoin1 = parametersUpdateVirtualMachineDomainJoin1.category('domain-join') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineDomainJoin1.command('domain-join') + removeparametersUpdateVirtualMachineDomainJoin1.command('remove') .description($('Remove domain-join in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43630,9 +43630,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDomainJoin2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDomainJoin2 = catparametersUpdateVirtualMachineDomainJoin2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineDomainJoin2 = parametersUpdateVirtualMachineDomainJoin2.category('add') + var addparametersUpdateVirtualMachineDomainJoin2 = parametersUpdateVirtualMachineDomainJoin2.category('domain-join') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineDomainJoin2.command('domain-join') + addparametersUpdateVirtualMachineDomainJoin2.command('add') .description($('Add domain-join in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "domainJoin" : {\r\n "credentials":{\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n },\r\n "domainToJoin":"",\r\n "ldapMachineObjectOU":"",\r\n "provisioning":{\r\n "accountData":""\r\n }\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43715,9 +43715,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineCredentials0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineCredentials0 = catparametersUpdateVirtualMachineCredentials0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineCredentials0 = parametersUpdateVirtualMachineCredentials0.category('set') + var setparametersUpdateVirtualMachineCredentials0 = parametersUpdateVirtualMachineCredentials0.category('credentials') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineCredentials0.command('credentials') + setparametersUpdateVirtualMachineCredentials0.command('set') .description($('Set credentials in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43786,9 +43786,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineCredentials1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineCredentials1 = catparametersUpdateVirtualMachineCredentials1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineCredentials1 = parametersUpdateVirtualMachineCredentials1.category('remove') + var removeparametersUpdateVirtualMachineCredentials1 = parametersUpdateVirtualMachineCredentials1.category('credentials') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineCredentials1.command('credentials') + removeparametersUpdateVirtualMachineCredentials1.command('remove') .description($('Remove credentials in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43841,9 +43841,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineCredentials2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineCredentials2 = catparametersUpdateVirtualMachineCredentials2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineCredentials2 = parametersUpdateVirtualMachineCredentials2.category('add') + var addparametersUpdateVirtualMachineCredentials2 = parametersUpdateVirtualMachineCredentials2.category('credentials') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineCredentials2.command('credentials') + addparametersUpdateVirtualMachineCredentials2.command('add') .description($('Add credentials in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "credentials" : {\r\n "domain":"",\r\n "password":"",\r\n "userName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43915,9 +43915,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineProvisioning0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineProvisioning0 = catparametersUpdateVirtualMachineProvisioning0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineProvisioning0 = parametersUpdateVirtualMachineProvisioning0.category('set') + var setparametersUpdateVirtualMachineProvisioning0 = parametersUpdateVirtualMachineProvisioning0.category('provisioning') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineProvisioning0.command('provisioning') + setparametersUpdateVirtualMachineProvisioning0.command('set') .description($('Set provisioning in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -43964,9 +43964,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineProvisioning1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineProvisioning1 = catparametersUpdateVirtualMachineProvisioning1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineProvisioning1 = parametersUpdateVirtualMachineProvisioning1.category('remove') + var removeparametersUpdateVirtualMachineProvisioning1 = parametersUpdateVirtualMachineProvisioning1.category('provisioning') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineProvisioning1.command('provisioning') + removeparametersUpdateVirtualMachineProvisioning1.command('remove') .description($('Remove provisioning in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44009,9 +44009,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineProvisioning2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineProvisioning2 = catparametersUpdateVirtualMachineProvisioning2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineProvisioning2 = parametersUpdateVirtualMachineProvisioning2.category('add') + var addparametersUpdateVirtualMachineProvisioning2 = parametersUpdateVirtualMachineProvisioning2.category('provisioning') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineProvisioning2.command('provisioning') + addparametersUpdateVirtualMachineProvisioning2.command('add') .description($('Add provisioning in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "provisioning" : {\r\n "accountData":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44061,9 +44061,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineInputEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineInputEndpoints0 = catparametersUpdateVirtualMachineInputEndpoints0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineInputEndpoints0 = parametersUpdateVirtualMachineInputEndpoints0.category('set') + var setparametersUpdateVirtualMachineInputEndpoints0 = parametersUpdateVirtualMachineInputEndpoints0.category('input-endpoints') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineInputEndpoints0.command('input-endpoints') + setparametersUpdateVirtualMachineInputEndpoints0.command('set') .description($('Set input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44248,9 +44248,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineInputEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineInputEndpoints1 = catparametersUpdateVirtualMachineInputEndpoints1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineInputEndpoints1 = parametersUpdateVirtualMachineInputEndpoints1.category('remove') + var removeparametersUpdateVirtualMachineInputEndpoints1 = parametersUpdateVirtualMachineInputEndpoints1.category('input-endpoints') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineInputEndpoints1.command('input-endpoints') + removeparametersUpdateVirtualMachineInputEndpoints1.command('remove') .description($('Remove input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44354,9 +44354,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineInputEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineInputEndpoints2 = catparametersUpdateVirtualMachineInputEndpoints2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineInputEndpoints2 = parametersUpdateVirtualMachineInputEndpoints2.category('add') + var addparametersUpdateVirtualMachineInputEndpoints2 = parametersUpdateVirtualMachineInputEndpoints2.category('input-endpoints') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineInputEndpoints2.command('input-endpoints') + addparametersUpdateVirtualMachineInputEndpoints2.command('add') .description($('Add input-endpoints in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "inputEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "endpointAcl":{\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n },\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44539,9 +44539,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineEndpointAcl1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineEndpointAcl1 = catparametersUpdateVirtualMachineEndpointAcl1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineEndpointAcl1 = parametersUpdateVirtualMachineEndpointAcl1.category('remove') + var removeparametersUpdateVirtualMachineEndpointAcl1 = parametersUpdateVirtualMachineEndpointAcl1.category('endpoint-acl') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineEndpointAcl1.command('endpoint-acl') + removeparametersUpdateVirtualMachineEndpointAcl1.command('remove') .description($('Remove endpoint-acl in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44585,9 +44585,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineEndpointAcl2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineEndpointAcl2 = catparametersUpdateVirtualMachineEndpointAcl2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineEndpointAcl2 = parametersUpdateVirtualMachineEndpointAcl2.category('add') + var addparametersUpdateVirtualMachineEndpointAcl2 = parametersUpdateVirtualMachineEndpointAcl2.category('endpoint-acl') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineEndpointAcl2.command('endpoint-acl') + addparametersUpdateVirtualMachineEndpointAcl2.command('add') .description($('Add endpoint-acl in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "endpointAcl" : {\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44637,9 +44637,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineRules0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineRules0 = catparametersUpdateVirtualMachineRules0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineRules0 = parametersUpdateVirtualMachineRules0.category('set') + var setparametersUpdateVirtualMachineRules0 = parametersUpdateVirtualMachineRules0.category('rules') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineRules0.command('rules') + setparametersUpdateVirtualMachineRules0.command('set') .description($('Set rules in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44725,9 +44725,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineRules1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineRules1 = catparametersUpdateVirtualMachineRules1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineRules1 = parametersUpdateVirtualMachineRules1.category('remove') + var removeparametersUpdateVirtualMachineRules1 = parametersUpdateVirtualMachineRules1.category('rules') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineRules1.command('rules') + removeparametersUpdateVirtualMachineRules1.command('remove') .description($('Remove rules in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44787,9 +44787,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineRules2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineRules2 = catparametersUpdateVirtualMachineRules2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineRules2 = parametersUpdateVirtualMachineRules2.category('add') + var addparametersUpdateVirtualMachineRules2 = parametersUpdateVirtualMachineRules2.category('rules') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineRules2.command('rules') + addparametersUpdateVirtualMachineRules2.command('add') .description($('Add rules in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44872,9 +44872,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineLoadBalancerProbe0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineLoadBalancerProbe0 = catparametersUpdateVirtualMachineLoadBalancerProbe0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineLoadBalancerProbe0 = parametersUpdateVirtualMachineLoadBalancerProbe0.category('set') + var setparametersUpdateVirtualMachineLoadBalancerProbe0 = parametersUpdateVirtualMachineLoadBalancerProbe0.category('load-balancer-probe') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineLoadBalancerProbe0.command('load-balancer-probe') + setparametersUpdateVirtualMachineLoadBalancerProbe0.command('set') .description($('Set load-balancer-probe in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -44966,9 +44966,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineLoadBalancerProbe1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineLoadBalancerProbe1 = catparametersUpdateVirtualMachineLoadBalancerProbe1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineLoadBalancerProbe1 = parametersUpdateVirtualMachineLoadBalancerProbe1.category('remove') + var removeparametersUpdateVirtualMachineLoadBalancerProbe1 = parametersUpdateVirtualMachineLoadBalancerProbe1.category('load-balancer-probe') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineLoadBalancerProbe1.command('load-balancer-probe') + removeparametersUpdateVirtualMachineLoadBalancerProbe1.command('remove') .description($('Remove load-balancer-probe in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45032,9 +45032,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineLoadBalancerProbe2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineLoadBalancerProbe2 = catparametersUpdateVirtualMachineLoadBalancerProbe2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineLoadBalancerProbe2 = parametersUpdateVirtualMachineLoadBalancerProbe2.category('add') + var addparametersUpdateVirtualMachineLoadBalancerProbe2 = parametersUpdateVirtualMachineLoadBalancerProbe2.category('load-balancer-probe') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineLoadBalancerProbe2.command('load-balancer-probe') + addparametersUpdateVirtualMachineLoadBalancerProbe2.command('add') .description($('Add load-balancer-probe in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45128,9 +45128,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineProtocol1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineProtocol1 = catparametersUpdateVirtualMachineProtocol1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineProtocol1 = parametersUpdateVirtualMachineProtocol1.category('remove') + var removeparametersUpdateVirtualMachineProtocol1 = parametersUpdateVirtualMachineProtocol1.category('protocol') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineProtocol1.command('protocol') + removeparametersUpdateVirtualMachineProtocol1.command('remove') .description($('Remove protocol in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45163,9 +45163,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineProtocol2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineProtocol2 = catparametersUpdateVirtualMachineProtocol2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineProtocol2 = parametersUpdateVirtualMachineProtocol2.category('add') + var addparametersUpdateVirtualMachineProtocol2 = parametersUpdateVirtualMachineProtocol2.category('protocol') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineProtocol2.command('protocol') + addparametersUpdateVirtualMachineProtocol2.command('add') .description($('Add protocol in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45204,9 +45204,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineNetworkInterfaces0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineNetworkInterfaces0 = catparametersUpdateVirtualMachineNetworkInterfaces0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineNetworkInterfaces0 = parametersUpdateVirtualMachineNetworkInterfaces0.category('set') + var setparametersUpdateVirtualMachineNetworkInterfaces0 = parametersUpdateVirtualMachineNetworkInterfaces0.category('network-interfaces') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineNetworkInterfaces0.command('network-interfaces') + setparametersUpdateVirtualMachineNetworkInterfaces0.command('set') .description($('Set network-interfaces in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45291,9 +45291,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineNetworkInterfaces1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineNetworkInterfaces1 = catparametersUpdateVirtualMachineNetworkInterfaces1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineNetworkInterfaces1 = parametersUpdateVirtualMachineNetworkInterfaces1.category('remove') + var removeparametersUpdateVirtualMachineNetworkInterfaces1 = parametersUpdateVirtualMachineNetworkInterfaces1.category('network-interfaces') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineNetworkInterfaces1.command('network-interfaces') + removeparametersUpdateVirtualMachineNetworkInterfaces1.command('remove') .description($('Remove network-interfaces in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45352,9 +45352,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineNetworkInterfaces2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineNetworkInterfaces2 = catparametersUpdateVirtualMachineNetworkInterfaces2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineNetworkInterfaces2 = parametersUpdateVirtualMachineNetworkInterfaces2.category('add') + var addparametersUpdateVirtualMachineNetworkInterfaces2 = parametersUpdateVirtualMachineNetworkInterfaces2.category('network-interfaces') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineNetworkInterfaces2.command('network-interfaces') + addparametersUpdateVirtualMachineNetworkInterfaces2.command('add') .description($('Add network-interfaces in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "networkInterfaces" : {\r\n "iPConfigurations":[\r\n {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ],\r\n "iPForwarding":"",\r\n "name":"",\r\n "networkSecurityGroup":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45437,9 +45437,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineIPConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineIPConfigurations0 = catparametersUpdateVirtualMachineIPConfigurations0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineIPConfigurations0 = parametersUpdateVirtualMachineIPConfigurations0.category('set') + var setparametersUpdateVirtualMachineIPConfigurations0 = parametersUpdateVirtualMachineIPConfigurations0.category('ip-configurations') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineIPConfigurations0.command('ip-configurations') + setparametersUpdateVirtualMachineIPConfigurations0.command('set') .description($('Set ip-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45503,9 +45503,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineIPConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineIPConfigurations1 = catparametersUpdateVirtualMachineIPConfigurations1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineIPConfigurations1 = parametersUpdateVirtualMachineIPConfigurations1.category('remove') + var removeparametersUpdateVirtualMachineIPConfigurations1 = parametersUpdateVirtualMachineIPConfigurations1.category('ip-configurations') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineIPConfigurations1.command('ip-configurations') + removeparametersUpdateVirtualMachineIPConfigurations1.command('remove') .description($('Remove ip-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45555,9 +45555,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineIPConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineIPConfigurations2 = catparametersUpdateVirtualMachineIPConfigurations2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineIPConfigurations2 = parametersUpdateVirtualMachineIPConfigurations2.category('add') + var addparametersUpdateVirtualMachineIPConfigurations2 = parametersUpdateVirtualMachineIPConfigurations2.category('ip-configurations') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineIPConfigurations2.command('ip-configurations') + addparametersUpdateVirtualMachineIPConfigurations2.command('add') .description($('Add ip-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "ipConfigurations" : {\r\n "staticVirtualNetworkIPAddress":"",\r\n "subnetName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45618,9 +45618,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicIPs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicIPs0 = catparametersUpdateVirtualMachinePublicIPs0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachinePublicIPs0 = parametersUpdateVirtualMachinePublicIPs0.category('set') + var setparametersUpdateVirtualMachinePublicIPs0 = parametersUpdateVirtualMachinePublicIPs0.category('public-ip') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachinePublicIPs0.command('public-ip') + setparametersUpdateVirtualMachinePublicIPs0.command('set') .description($('Set public-ip in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45694,9 +45694,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicIPs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicIPs1 = catparametersUpdateVirtualMachinePublicIPs1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachinePublicIPs1 = parametersUpdateVirtualMachinePublicIPs1.category('remove') + var removeparametersUpdateVirtualMachinePublicIPs1 = parametersUpdateVirtualMachinePublicIPs1.category('public-ip') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachinePublicIPs1.command('public-ip') + removeparametersUpdateVirtualMachinePublicIPs1.command('remove') .description($('Remove public-ip in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45750,9 +45750,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicIPs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicIPs2 = catparametersUpdateVirtualMachinePublicIPs2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachinePublicIPs2 = parametersUpdateVirtualMachinePublicIPs2.category('add') + var addparametersUpdateVirtualMachinePublicIPs2 = parametersUpdateVirtualMachinePublicIPs2.category('public-ip') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachinePublicIPs2.command('public-ip') + addparametersUpdateVirtualMachinePublicIPs2.command('add') .description($('Add public-ip in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicIPs" : {\r\n "domainNameLabel":"",\r\n "idleTimeoutInMinutes":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45824,9 +45824,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineSshSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineSshSettings1 = catparametersUpdateVirtualMachineSshSettings1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineSshSettings1 = parametersUpdateVirtualMachineSshSettings1.category('remove') + var removeparametersUpdateVirtualMachineSshSettings1 = parametersUpdateVirtualMachineSshSettings1.category('ssh-settings') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineSshSettings1.command('ssh-settings') + removeparametersUpdateVirtualMachineSshSettings1.command('remove') .description($('Remove ssh-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45874,9 +45874,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineSshSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineSshSettings2 = catparametersUpdateVirtualMachineSshSettings2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineSshSettings2 = parametersUpdateVirtualMachineSshSettings2.category('add') + var addparametersUpdateVirtualMachineSshSettings2 = parametersUpdateVirtualMachineSshSettings2.category('ssh-settings') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineSshSettings2.command('ssh-settings') + addparametersUpdateVirtualMachineSshSettings2.command('add') .description($('Add ssh-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "sshSettings" : {\r\n "keyPairs":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ],\r\n "publicKeys":[\r\n {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -45937,9 +45937,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineKeyPairs0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineKeyPairs0 = catparametersUpdateVirtualMachineKeyPairs0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineKeyPairs0 = parametersUpdateVirtualMachineKeyPairs0.category('set') + var setparametersUpdateVirtualMachineKeyPairs0 = parametersUpdateVirtualMachineKeyPairs0.category('key-pairs') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineKeyPairs0.command('key-pairs') + setparametersUpdateVirtualMachineKeyPairs0.command('set') .description($('Set key-pairs in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46002,9 +46002,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineKeyPairs1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineKeyPairs1 = catparametersUpdateVirtualMachineKeyPairs1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineKeyPairs1 = parametersUpdateVirtualMachineKeyPairs1.category('remove') + var removeparametersUpdateVirtualMachineKeyPairs1 = parametersUpdateVirtualMachineKeyPairs1.category('key-pairs') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineKeyPairs1.command('key-pairs') + removeparametersUpdateVirtualMachineKeyPairs1.command('remove') .description($('Remove key-pairs in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46053,9 +46053,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineKeyPairs2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineKeyPairs2 = catparametersUpdateVirtualMachineKeyPairs2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineKeyPairs2 = parametersUpdateVirtualMachineKeyPairs2.category('add') + var addparametersUpdateVirtualMachineKeyPairs2 = parametersUpdateVirtualMachineKeyPairs2.category('key-pairs') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineKeyPairs2.command('key-pairs') + addparametersUpdateVirtualMachineKeyPairs2.command('add') .description($('Add key-pairs in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "keyPairs" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46116,9 +46116,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicKeys0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicKeys0 = catparametersUpdateVirtualMachinePublicKeys0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachinePublicKeys0 = parametersUpdateVirtualMachinePublicKeys0.category('set') + var setparametersUpdateVirtualMachinePublicKeys0 = parametersUpdateVirtualMachinePublicKeys0.category('public-keys') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachinePublicKeys0.command('public-keys') + setparametersUpdateVirtualMachinePublicKeys0.command('set') .description($('Set public-keys in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46181,9 +46181,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicKeys1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicKeys1 = catparametersUpdateVirtualMachinePublicKeys1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachinePublicKeys1 = parametersUpdateVirtualMachinePublicKeys1.category('remove') + var removeparametersUpdateVirtualMachinePublicKeys1 = parametersUpdateVirtualMachinePublicKeys1.category('public-keys') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachinePublicKeys1.command('public-keys') + removeparametersUpdateVirtualMachinePublicKeys1.command('remove') .description($('Remove public-keys in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46232,9 +46232,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachinePublicKeys2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachinePublicKeys2 = catparametersUpdateVirtualMachinePublicKeys2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachinePublicKeys2 = parametersUpdateVirtualMachinePublicKeys2.category('add') + var addparametersUpdateVirtualMachinePublicKeys2 = parametersUpdateVirtualMachinePublicKeys2.category('public-keys') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachinePublicKeys2.command('public-keys') + addparametersUpdateVirtualMachinePublicKeys2.command('add') .description($('Add public-keys in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "publicKeys" : {\r\n "fingerprint":"",\r\n "path":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46295,9 +46295,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineStoredCertificateSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineStoredCertificateSettings0 = catparametersUpdateVirtualMachineStoredCertificateSettings0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineStoredCertificateSettings0 = parametersUpdateVirtualMachineStoredCertificateSettings0.category('set') + var setparametersUpdateVirtualMachineStoredCertificateSettings0 = parametersUpdateVirtualMachineStoredCertificateSettings0.category('stored-certificate-settings') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineStoredCertificateSettings0.command('stored-certificate-settings') + setparametersUpdateVirtualMachineStoredCertificateSettings0.command('set') .description($('Set stored-certificate-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46360,9 +46360,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineStoredCertificateSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineStoredCertificateSettings1 = catparametersUpdateVirtualMachineStoredCertificateSettings1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineStoredCertificateSettings1 = parametersUpdateVirtualMachineStoredCertificateSettings1.category('remove') + var removeparametersUpdateVirtualMachineStoredCertificateSettings1 = parametersUpdateVirtualMachineStoredCertificateSettings1.category('stored-certificate-settings') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineStoredCertificateSettings1.command('stored-certificate-settings') + removeparametersUpdateVirtualMachineStoredCertificateSettings1.command('remove') .description($('Remove stored-certificate-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46411,9 +46411,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineStoredCertificateSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineStoredCertificateSettings2 = catparametersUpdateVirtualMachineStoredCertificateSettings2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineStoredCertificateSettings2 = parametersUpdateVirtualMachineStoredCertificateSettings2.category('add') + var addparametersUpdateVirtualMachineStoredCertificateSettings2 = parametersUpdateVirtualMachineStoredCertificateSettings2.category('stored-certificate-settings') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineStoredCertificateSettings2.command('stored-certificate-settings') + addparametersUpdateVirtualMachineStoredCertificateSettings2.command('add') .description($('Add stored-certificate-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "storedCertificateSettings" : {\r\n "storeName":"",\r\n "thumbprint":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46474,9 +46474,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineSubnetNames0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineSubnetNames0 = catparametersUpdateVirtualMachineSubnetNames0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineSubnetNames0 = parametersUpdateVirtualMachineSubnetNames0.category('set') + var setparametersUpdateVirtualMachineSubnetNames0 = parametersUpdateVirtualMachineSubnetNames0.category('subnet-names') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineSubnetNames0.command('subnet-names') + setparametersUpdateVirtualMachineSubnetNames0.command('set') .description($('Set subnet-names in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46517,9 +46517,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineSubnetNames1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineSubnetNames1 = catparametersUpdateVirtualMachineSubnetNames1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineSubnetNames1 = parametersUpdateVirtualMachineSubnetNames1.category('remove') + var removeparametersUpdateVirtualMachineSubnetNames1 = parametersUpdateVirtualMachineSubnetNames1.category('subnet-names') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineSubnetNames1.command('subnet-names') + removeparametersUpdateVirtualMachineSubnetNames1.command('remove') .description($('Remove subnet-names in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46552,9 +46552,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineSubnetNames2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineSubnetNames2 = catparametersUpdateVirtualMachineSubnetNames2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineSubnetNames2 = parametersUpdateVirtualMachineSubnetNames2.category('add') + var addparametersUpdateVirtualMachineSubnetNames2 = parametersUpdateVirtualMachineSubnetNames2.category('subnet-names') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineSubnetNames2.command('subnet-names') + addparametersUpdateVirtualMachineSubnetNames2.command('add') .description($('Add subnet-names in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "subnetNames" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46593,9 +46593,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineWindowsRemoteManagement1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineWindowsRemoteManagement1 = catparametersUpdateVirtualMachineWindowsRemoteManagement1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineWindowsRemoteManagement1 = parametersUpdateVirtualMachineWindowsRemoteManagement1.category('remove') + var removeparametersUpdateVirtualMachineWindowsRemoteManagement1 = parametersUpdateVirtualMachineWindowsRemoteManagement1.category('windows-remote-management') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineWindowsRemoteManagement1.command('windows-remote-management') + removeparametersUpdateVirtualMachineWindowsRemoteManagement1.command('remove') .description($('Remove windows-remote-management in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46638,9 +46638,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineWindowsRemoteManagement2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineWindowsRemoteManagement2 = catparametersUpdateVirtualMachineWindowsRemoteManagement2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineWindowsRemoteManagement2 = parametersUpdateVirtualMachineWindowsRemoteManagement2.category('add') + var addparametersUpdateVirtualMachineWindowsRemoteManagement2 = parametersUpdateVirtualMachineWindowsRemoteManagement2.category('windows-remote-management') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineWindowsRemoteManagement2.command('windows-remote-management') + addparametersUpdateVirtualMachineWindowsRemoteManagement2.command('add') .description($('Add windows-remote-management in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "windowsRemoteManagement" : {\r\n "listeners":[\r\n {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ]\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46690,9 +46690,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineListeners0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineListeners0 = catparametersUpdateVirtualMachineListeners0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineListeners0 = parametersUpdateVirtualMachineListeners0.category('set') + var setparametersUpdateVirtualMachineListeners0 = parametersUpdateVirtualMachineListeners0.category('listeners') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineListeners0.command('listeners') + setparametersUpdateVirtualMachineListeners0.command('set') .description($('Set listeners in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46755,9 +46755,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineListeners1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineListeners1 = catparametersUpdateVirtualMachineListeners1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineListeners1 = parametersUpdateVirtualMachineListeners1.category('remove') + var removeparametersUpdateVirtualMachineListeners1 = parametersUpdateVirtualMachineListeners1.category('listeners') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineListeners1.command('listeners') + removeparametersUpdateVirtualMachineListeners1.command('remove') .description($('Remove listeners in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46806,9 +46806,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineListeners2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineListeners2 = catparametersUpdateVirtualMachineListeners2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineListeners2 = parametersUpdateVirtualMachineListeners2.category('add') + var addparametersUpdateVirtualMachineListeners2 = parametersUpdateVirtualMachineListeners2.category('listeners') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineListeners2.command('listeners') + addparametersUpdateVirtualMachineListeners2.command('add') .description($('Add listeners in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "listeners" : {\r\n "certificateThumbprint":"",\r\n "listenerType":0\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46869,9 +46869,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineListenerType1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineListenerType1 = catparametersUpdateVirtualMachineListenerType1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineListenerType1 = parametersUpdateVirtualMachineListenerType1.category('remove') + var removeparametersUpdateVirtualMachineListenerType1 = parametersUpdateVirtualMachineListenerType1.category('listener-type') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineListenerType1.command('listener-type') + removeparametersUpdateVirtualMachineListenerType1.command('remove') .description($('Remove listener-type in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46904,9 +46904,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineListenerType2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineListenerType2 = catparametersUpdateVirtualMachineListenerType2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineListenerType2 = parametersUpdateVirtualMachineListenerType2.category('add') + var addparametersUpdateVirtualMachineListenerType2 = parametersUpdateVirtualMachineListenerType2.category('listener-type') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineListenerType2.command('listener-type') + addparametersUpdateVirtualMachineListenerType2.command('add') .description($('Add listener-type in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "listenerType" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -46945,9 +46945,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDataVirtualHardDisks0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDataVirtualHardDisks0 = catparametersUpdateVirtualMachineDataVirtualHardDisks0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineDataVirtualHardDisks0 = parametersUpdateVirtualMachineDataVirtualHardDisks0.category('set') + var setparametersUpdateVirtualMachineDataVirtualHardDisks0 = parametersUpdateVirtualMachineDataVirtualHardDisks0.category('data-virtual-hard-disks') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineDataVirtualHardDisks0.command('data-virtual-hard-disks') + setparametersUpdateVirtualMachineDataVirtualHardDisks0.command('set') .description($('Set data-virtual-hard-disks in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47075,9 +47075,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDataVirtualHardDisks1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDataVirtualHardDisks1 = catparametersUpdateVirtualMachineDataVirtualHardDisks1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineDataVirtualHardDisks1 = parametersUpdateVirtualMachineDataVirtualHardDisks1.category('remove') + var removeparametersUpdateVirtualMachineDataVirtualHardDisks1 = parametersUpdateVirtualMachineDataVirtualHardDisks1.category('data-virtual-hard-disks') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineDataVirtualHardDisks1.command('data-virtual-hard-disks') + removeparametersUpdateVirtualMachineDataVirtualHardDisks1.command('remove') .description($('Remove data-virtual-hard-disks in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47155,9 +47155,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDataVirtualHardDisks2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDataVirtualHardDisks2 = catparametersUpdateVirtualMachineDataVirtualHardDisks2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineDataVirtualHardDisks2 = parametersUpdateVirtualMachineDataVirtualHardDisks2.category('add') + var addparametersUpdateVirtualMachineDataVirtualHardDisks2 = parametersUpdateVirtualMachineDataVirtualHardDisks2.category('data-virtual-hard-disks') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineDataVirtualHardDisks2.command('data-virtual-hard-disks') + addparametersUpdateVirtualMachineDataVirtualHardDisks2.command('add') .description($('Add data-virtual-hard-disks in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataVirtualHardDisks" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "logicalDiskSizeInGB":null,\r\n "logicalUnitNumber":null,\r\n "mediaLink":"",\r\n "name":"",\r\n "sourceMediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47284,9 +47284,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDebugSettings0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDebugSettings0 = catparametersUpdateVirtualMachineDebugSettings0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineDebugSettings0 = parametersUpdateVirtualMachineDebugSettings0.category('set') + var setparametersUpdateVirtualMachineDebugSettings0 = parametersUpdateVirtualMachineDebugSettings0.category('debug-settings') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineDebugSettings0.command('debug-settings') + setparametersUpdateVirtualMachineDebugSettings0.command('set') .description($('Set debug-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47354,9 +47354,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDebugSettings1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDebugSettings1 = catparametersUpdateVirtualMachineDebugSettings1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineDebugSettings1 = parametersUpdateVirtualMachineDebugSettings1.category('remove') + var removeparametersUpdateVirtualMachineDebugSettings1 = parametersUpdateVirtualMachineDebugSettings1.category('debug-settings') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineDebugSettings1.command('debug-settings') + removeparametersUpdateVirtualMachineDebugSettings1.command('remove') .description($('Remove debug-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47408,9 +47408,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineDebugSettings2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineDebugSettings2 = catparametersUpdateVirtualMachineDebugSettings2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineDebugSettings2 = parametersUpdateVirtualMachineDebugSettings2.category('add') + var addparametersUpdateVirtualMachineDebugSettings2 = parametersUpdateVirtualMachineDebugSettings2.category('debug-settings') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineDebugSettings2.command('debug-settings') + addparametersUpdateVirtualMachineDebugSettings2.command('add') .description($('Add debug-settings in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "debugSettings" : {\r\n "bootDiagnosticsEnabled":false,\r\n "consoleScreenshotBlobUri":"",\r\n "serialOutputBlobUri":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47482,9 +47482,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSVirtualHardDisk0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineOSVirtualHardDisk0 = catparametersUpdateVirtualMachineOSVirtualHardDisk0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineOSVirtualHardDisk0 = parametersUpdateVirtualMachineOSVirtualHardDisk0.category('set') + var setparametersUpdateVirtualMachineOSVirtualHardDisk0 = parametersUpdateVirtualMachineOSVirtualHardDisk0.category('os-virtual-hard-disk') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineOSVirtualHardDisk0.command('os-virtual-hard-disk') + setparametersUpdateVirtualMachineOSVirtualHardDisk0.command('set') .description($('Set os-virtual-hard-disk in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47618,9 +47618,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSVirtualHardDisk1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineOSVirtualHardDisk1 = catparametersUpdateVirtualMachineOSVirtualHardDisk1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineOSVirtualHardDisk1 = parametersUpdateVirtualMachineOSVirtualHardDisk1.category('remove') + var removeparametersUpdateVirtualMachineOSVirtualHardDisk1 = parametersUpdateVirtualMachineOSVirtualHardDisk1.category('os-virtual-hard-disk') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineOSVirtualHardDisk1.command('os-virtual-hard-disk') + removeparametersUpdateVirtualMachineOSVirtualHardDisk1.command('remove') .description($('Remove os-virtual-hard-disk in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47702,9 +47702,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSVirtualHardDisk2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineOSVirtualHardDisk2 = catparametersUpdateVirtualMachineOSVirtualHardDisk2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineOSVirtualHardDisk2 = parametersUpdateVirtualMachineOSVirtualHardDisk2.category('add') + var addparametersUpdateVirtualMachineOSVirtualHardDisk2 = parametersUpdateVirtualMachineOSVirtualHardDisk2.category('os-virtual-hard-disk') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineOSVirtualHardDisk2.command('os-virtual-hard-disk') + addparametersUpdateVirtualMachineOSVirtualHardDisk2.command('add') .description($('Add os-virtual-hard-disk in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSVirtualHardDisk" : {\r\n "hostCaching":"",\r\n "iOType":"",\r\n "label":"",\r\n "mediaLink":"",\r\n "name":"",\r\n "operatingSystem":"",\r\n "remoteSourceImageLink":"",\r\n "resizedSizeInGB":null,\r\n "sourceImageName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47842,9 +47842,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionReferences0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionReferences0 = catparametersUpdateVirtualMachineResourceExtensionReferences0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineResourceExtensionReferences0 = parametersUpdateVirtualMachineResourceExtensionReferences0.category('set') + var setparametersUpdateVirtualMachineResourceExtensionReferences0 = parametersUpdateVirtualMachineResourceExtensionReferences0.category('resource-extension-references') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineResourceExtensionReferences0.command('resource-extension-references') + setparametersUpdateVirtualMachineResourceExtensionReferences0.command('set') .description($('Set resource-extension-references in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -47962,9 +47962,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionReferences1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionReferences1 = catparametersUpdateVirtualMachineResourceExtensionReferences1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineResourceExtensionReferences1 = parametersUpdateVirtualMachineResourceExtensionReferences1.category('remove') + var removeparametersUpdateVirtualMachineResourceExtensionReferences1 = parametersUpdateVirtualMachineResourceExtensionReferences1.category('resource-extension-references') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineResourceExtensionReferences1.command('resource-extension-references') + removeparametersUpdateVirtualMachineResourceExtensionReferences1.command('remove') .description($('Remove resource-extension-references in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48037,9 +48037,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionReferences2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionReferences2 = catparametersUpdateVirtualMachineResourceExtensionReferences2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineResourceExtensionReferences2 = parametersUpdateVirtualMachineResourceExtensionReferences2.category('add') + var addparametersUpdateVirtualMachineResourceExtensionReferences2 = parametersUpdateVirtualMachineResourceExtensionReferences2.category('resource-extension-references') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineResourceExtensionReferences2.command('resource-extension-references') + addparametersUpdateVirtualMachineResourceExtensionReferences2.command('add') .description($('Add resource-extension-references in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionReferences" : {\r\n "forceUpdate":null,\r\n "name":"",\r\n "publisher":"",\r\n "referenceName":"",\r\n "resourceExtensionParameterValues":[\r\n {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ],\r\n "state":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48156,9 +48156,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionParameterValues0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionParameterValues0 = catparametersUpdateVirtualMachineResourceExtensionParameterValues0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateVirtualMachineResourceExtensionParameterValues0 = parametersUpdateVirtualMachineResourceExtensionParameterValues0.category('set') + var setparametersUpdateVirtualMachineResourceExtensionParameterValues0 = parametersUpdateVirtualMachineResourceExtensionParameterValues0.category('resource-extension-parameter-values') .description($('Commands to set components of virtual-machine in update-parameters file.')); - setparametersUpdateVirtualMachineResourceExtensionParameterValues0.command('resource-extension-parameter-values') + setparametersUpdateVirtualMachineResourceExtensionParameterValues0.command('set') .description($('Set resource-extension-parameter-values in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48232,9 +48232,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionParameterValues1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionParameterValues1 = catparametersUpdateVirtualMachineResourceExtensionParameterValues1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateVirtualMachineResourceExtensionParameterValues1 = parametersUpdateVirtualMachineResourceExtensionParameterValues1.category('remove') + var removeparametersUpdateVirtualMachineResourceExtensionParameterValues1 = parametersUpdateVirtualMachineResourceExtensionParameterValues1.category('resource-extension-parameter-values') .description($('Commands to remove components of virtual-machine in update-parameters file.')); - removeparametersUpdateVirtualMachineResourceExtensionParameterValues1.command('resource-extension-parameter-values') + removeparametersUpdateVirtualMachineResourceExtensionParameterValues1.command('remove') .description($('Remove resource-extension-parameter-values in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48288,9 +48288,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineResourceExtensionParameterValues2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateVirtualMachineResourceExtensionParameterValues2 = catparametersUpdateVirtualMachineResourceExtensionParameterValues2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateVirtualMachineResourceExtensionParameterValues2 = parametersUpdateVirtualMachineResourceExtensionParameterValues2.category('add') + var addparametersUpdateVirtualMachineResourceExtensionParameterValues2 = parametersUpdateVirtualMachineResourceExtensionParameterValues2.category('resource-extension-parameter-values') .description($('Commands to add components of virtual-machine in update-parameters file.')); - addparametersUpdateVirtualMachineResourceExtensionParameterValues2.command('resource-extension-parameter-values') + addparametersUpdateVirtualMachineResourceExtensionParameterValues2.command('add') .description($('Add resource-extension-parameter-values in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "resourceExtensionParameterValues" : {\r\n "key":"",\r\n "type":"",\r\n "value":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48504,9 +48504,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1.category('remove') + var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1.category('virtual-machine-update-load-balanced-set-parameters') .description($('Commands to remove components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - removeparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1.command('virtual-machine-update-load-balanced-set-parameters') + removeparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters1.command('remove') .description($('Remove virtual-machine-update-load-balanced-set-parameters in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n{\r\n "loadBalancedEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ],\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48548,9 +48548,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2.category('add') + var addparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2.category('virtual-machine-update-load-balanced-set-parameters') .description($('Commands to add components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - addparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2.command('virtual-machine-update-load-balanced-set-parameters') + addparametersUpdateLoadBalancedEndpointSetVirtualMachineVirtualMachineUpdateLoadBalancedSetParameters2.command('add') .description($('Add virtual-machine-update-load-balanced-set-parameters in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n{\r\n "loadBalancedEndpoints":[\r\n {\r\n "enableDirectServerReturn":null,\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ],\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48600,9 +48600,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0.category('set') + var setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0.category('load-balanced-endpoints') .description($('Commands to set components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0.command('load-balanced-endpoints') + setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints0.command('set') .description($('Set load-balanced-endpoints in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancedEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ],\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48786,9 +48786,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1.category('remove') + var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1.category('load-balanced-endpoints') .description($('Commands to remove components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1.command('load-balanced-endpoints') + removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints1.command('remove') .description($('Remove load-balanced-endpoints in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancedEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ],\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -48891,9 +48891,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2.category('add') + var addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2.category('load-balanced-endpoints') .description($('Commands to add components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2.command('load-balanced-endpoints') + addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancedEndpoints2.command('add') .description($('Add load-balanced-endpoints in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancedEndpoints" : {\r\n "enableDirectServerReturn":null,\r\n "idleTimeoutInMinutes":null,\r\n "loadBalancedEndpointSetName":"",\r\n "loadBalancerDistribution":"",\r\n "loadBalancerName":"",\r\n "loadBalancerProbe":{\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n },\r\n "localPort":null,\r\n "name":"",\r\n "port":null,\r\n "protocol":"",\r\n "rules":[\r\n {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ],\r\n "virtualIPAddress":"",\r\n "virtualIPName":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49076,9 +49076,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0.category('set') + var setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0.category('load-balancer-probe') .description($('Commands to set components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0.command('load-balancer-probe') + setparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe0.command('set') .description($('Set load-balancer-probe in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49169,9 +49169,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1.category('remove') + var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1.category('load-balancer-probe') .description($('Commands to remove components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1.command('load-balancer-probe') + removeparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe1.command('remove') .description($('Remove load-balancer-probe in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49234,9 +49234,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2.category('add') + var addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2.category('load-balancer-probe') .description($('Commands to add components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2.command('load-balancer-probe') + addparametersUpdateLoadBalancedEndpointSetVirtualMachineLoadBalancerProbe2.command('add') .description($('Add load-balancer-probe in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "loadBalancerProbe" : {\r\n "intervalInSeconds":null,\r\n "path":"",\r\n "port":0,\r\n "protocol":0,\r\n "timeoutInSeconds":null\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49330,9 +49330,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1.category('remove') + var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1.category('protocol') .description($('Commands to remove components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - removeparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1.command('protocol') + removeparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol1.command('remove') .description($('Remove protocol in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49364,9 +49364,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2.category('add') + var addparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2.category('protocol') .description($('Commands to add components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - addparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2.command('protocol') + addparametersUpdateLoadBalancedEndpointSetVirtualMachineProtocol2.command('add') .description($('Add protocol in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "protocol" : 0\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49405,9 +49405,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineRules0 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var setparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules0.category('set') + var setparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules0.category('rules') .description($('Commands to set components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - setparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0.command('rules') + setparametersUpdateLoadBalancedEndpointSetVirtualMachineRules0.command('set') .description($('Set rules in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49492,9 +49492,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineRules1 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules1.category('remove') + var removeparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules1.category('rules') .description($('Commands to remove components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - removeparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1.command('rules') + removeparametersUpdateLoadBalancedEndpointSetVirtualMachineRules1.command('remove') .description($('Remove rules in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49553,9 +49553,9 @@ exports.init = function (cli) { var catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine'); var parametersUpdateLoadBalancedEndpointSetVirtualMachineRules2 = catparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2.category('update-load-balanced-endpoint-set-parameters') .description($('Commands to manage configuration of virtual-machine in the parameter file.')); - var addparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules2.category('add') + var addparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2 = parametersUpdateLoadBalancedEndpointSetVirtualMachineRules2.category('rules') .description($('Commands to add components of virtual-machine in update-load-balanced-endpoint-set-parameters file.')); - addparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2.command('rules') + addparametersUpdateLoadBalancedEndpointSetVirtualMachineRules2.command('add') .description($('Add rules in update-load-balanced-endpoint-set-parameters string or files, e.g. \r\n {\r\n ...\r\n "rules" : {\r\n "action":"",\r\n "description":"",\r\n "order":null,\r\n "remoteSubnet":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49751,9 +49751,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0 = catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0.category('set') + var setparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0.category('virtual-machine-os-image-create-parameters') .description($('Commands to set components of virtual-machine-os-image in create-parameters file.')); - setparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0.command('virtual-machine-os-image-create-parameters') + setparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters0.command('set') .description($('Set virtual-machine-os-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":false,\r\n "label":"",\r\n "language":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":false,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -49953,9 +49953,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1 = catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1.category('remove') + var removeparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1.category('virtual-machine-os-image-create-parameters') .description($('Commands to remove components of virtual-machine-os-image in create-parameters file.')); - removeparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1.command('virtual-machine-os-image-create-parameters') + removeparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters1.command('remove') .description($('Remove virtual-machine-os-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":false,\r\n "label":"",\r\n "language":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":false,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50067,9 +50067,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2 = catparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2.category('add') + var addparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2 = parametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2.category('virtual-machine-os-image-create-parameters') .description($('Commands to add components of virtual-machine-os-image in create-parameters file.')); - addparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2.command('virtual-machine-os-image-create-parameters') + addparametersCreateVirtualMachineOSImageVirtualMachineOSImageCreateParameters2.command('add') .description($('Add virtual-machine-os-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":false,\r\n "label":"",\r\n "language":"",\r\n "mediaLinkUri":"",\r\n "name":"",\r\n "operatingSystemType":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":false,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50498,9 +50498,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0 = catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0.category('set') + var setparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0.category('virtual-machine-os-image-replicate-parameters') .description($('Commands to set components of virtual-machine-os-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0.command('virtual-machine-os-image-replicate-parameters') + setparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters0.command('set') .description($('Set virtual-machine-os-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50568,9 +50568,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1 = catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1.category('remove') + var removeparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1.category('virtual-machine-os-image-replicate-parameters') .description($('Commands to remove components of virtual-machine-os-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1.command('virtual-machine-os-image-replicate-parameters') + removeparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters1.command('remove') .description($('Remove virtual-machine-os-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50622,9 +50622,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2 = catparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2.category('add') + var addparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2 = parametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2.category('virtual-machine-os-image-replicate-parameters') .description($('Commands to add components of virtual-machine-os-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2.command('virtual-machine-os-image-replicate-parameters') + addparametersReplicateVirtualMachineOSImageVirtualMachineOSImageReplicateParameters2.command('add') .description($('Add virtual-machine-os-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50696,9 +50696,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageComputeImageAttributes0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageComputeImageAttributes0 = catparametersReplicateVirtualMachineOSImageComputeImageAttributes0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersReplicateVirtualMachineOSImageComputeImageAttributes0 = parametersReplicateVirtualMachineOSImageComputeImageAttributes0.category('set') + var setparametersReplicateVirtualMachineOSImageComputeImageAttributes0 = parametersReplicateVirtualMachineOSImageComputeImageAttributes0.category('compute-image-attributes') .description($('Commands to set components of virtual-machine-os-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineOSImageComputeImageAttributes0.command('compute-image-attributes') + setparametersReplicateVirtualMachineOSImageComputeImageAttributes0.command('set') .description($('Set compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50766,9 +50766,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageComputeImageAttributes1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageComputeImageAttributes1 = catparametersReplicateVirtualMachineOSImageComputeImageAttributes1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersReplicateVirtualMachineOSImageComputeImageAttributes1 = parametersReplicateVirtualMachineOSImageComputeImageAttributes1.category('remove') + var removeparametersReplicateVirtualMachineOSImageComputeImageAttributes1 = parametersReplicateVirtualMachineOSImageComputeImageAttributes1.category('compute-image-attributes') .description($('Commands to remove components of virtual-machine-os-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineOSImageComputeImageAttributes1.command('compute-image-attributes') + removeparametersReplicateVirtualMachineOSImageComputeImageAttributes1.command('remove') .description($('Remove compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50820,9 +50820,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageComputeImageAttributes2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageComputeImageAttributes2 = catparametersReplicateVirtualMachineOSImageComputeImageAttributes2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersReplicateVirtualMachineOSImageComputeImageAttributes2 = parametersReplicateVirtualMachineOSImageComputeImageAttributes2.category('add') + var addparametersReplicateVirtualMachineOSImageComputeImageAttributes2 = parametersReplicateVirtualMachineOSImageComputeImageAttributes2.category('compute-image-attributes') .description($('Commands to add components of virtual-machine-os-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineOSImageComputeImageAttributes2.command('compute-image-attributes') + addparametersReplicateVirtualMachineOSImageComputeImageAttributes2.command('add') .description($('Add compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50894,9 +50894,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0 = catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0.category('set') + var setparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0.category('marketplace-image-attributes') .description($('Commands to set components of virtual-machine-os-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0.command('marketplace-image-attributes') + setparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes0.command('set') .description($('Set marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -50953,9 +50953,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1 = catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1.category('remove') + var removeparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1.category('marketplace-image-attributes') .description($('Commands to remove components of virtual-machine-os-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1.command('marketplace-image-attributes') + removeparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes1.command('remove') .description($('Remove marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51002,9 +51002,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2 = catparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2.category('add') + var addparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2 = parametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2.category('marketplace-image-attributes') .description($('Commands to add components of virtual-machine-os-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2.command('marketplace-image-attributes') + addparametersReplicateVirtualMachineOSImageMarketplaceImageAttributes2.command('add') .description($('Add marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51065,9 +51065,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImagePlan0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImagePlan0 = catparametersReplicateVirtualMachineOSImagePlan0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersReplicateVirtualMachineOSImagePlan0 = parametersReplicateVirtualMachineOSImagePlan0.category('set') + var setparametersReplicateVirtualMachineOSImagePlan0 = parametersReplicateVirtualMachineOSImagePlan0.category('plan') .description($('Commands to set components of virtual-machine-os-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineOSImagePlan0.command('plan') + setparametersReplicateVirtualMachineOSImagePlan0.command('set') .description($('Set plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51135,9 +51135,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImagePlan1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImagePlan1 = catparametersReplicateVirtualMachineOSImagePlan1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersReplicateVirtualMachineOSImagePlan1 = parametersReplicateVirtualMachineOSImagePlan1.category('remove') + var removeparametersReplicateVirtualMachineOSImagePlan1 = parametersReplicateVirtualMachineOSImagePlan1.category('plan') .description($('Commands to remove components of virtual-machine-os-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineOSImagePlan1.command('plan') + removeparametersReplicateVirtualMachineOSImagePlan1.command('remove') .description($('Remove plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51189,9 +51189,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImagePlan2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImagePlan2 = catparametersReplicateVirtualMachineOSImagePlan2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersReplicateVirtualMachineOSImagePlan2 = parametersReplicateVirtualMachineOSImagePlan2.category('add') + var addparametersReplicateVirtualMachineOSImagePlan2 = parametersReplicateVirtualMachineOSImagePlan2.category('plan') .description($('Commands to add components of virtual-machine-os-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineOSImagePlan2.command('plan') + addparametersReplicateVirtualMachineOSImagePlan2.command('add') .description($('Add plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51263,9 +51263,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageTargetLocations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageTargetLocations0 = catparametersReplicateVirtualMachineOSImageTargetLocations0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersReplicateVirtualMachineOSImageTargetLocations0 = parametersReplicateVirtualMachineOSImageTargetLocations0.category('set') + var setparametersReplicateVirtualMachineOSImageTargetLocations0 = parametersReplicateVirtualMachineOSImageTargetLocations0.category('target-locations') .description($('Commands to set components of virtual-machine-os-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineOSImageTargetLocations0.command('target-locations') + setparametersReplicateVirtualMachineOSImageTargetLocations0.command('set') .description($('Set target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51305,9 +51305,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageTargetLocations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageTargetLocations1 = catparametersReplicateVirtualMachineOSImageTargetLocations1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersReplicateVirtualMachineOSImageTargetLocations1 = parametersReplicateVirtualMachineOSImageTargetLocations1.category('remove') + var removeparametersReplicateVirtualMachineOSImageTargetLocations1 = parametersReplicateVirtualMachineOSImageTargetLocations1.category('target-locations') .description($('Commands to remove components of virtual-machine-os-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineOSImageTargetLocations1.command('target-locations') + removeparametersReplicateVirtualMachineOSImageTargetLocations1.command('remove') .description($('Remove target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51339,9 +51339,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineOSImageTargetLocations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersReplicateVirtualMachineOSImageTargetLocations2 = catparametersReplicateVirtualMachineOSImageTargetLocations2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersReplicateVirtualMachineOSImageTargetLocations2 = parametersReplicateVirtualMachineOSImageTargetLocations2.category('add') + var addparametersReplicateVirtualMachineOSImageTargetLocations2 = parametersReplicateVirtualMachineOSImageTargetLocations2.category('target-locations') .description($('Commands to add components of virtual-machine-os-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineOSImageTargetLocations2.command('target-locations') + addparametersReplicateVirtualMachineOSImageTargetLocations2.command('add') .description($('Add target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51554,9 +51554,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0 = catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var setparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0.category('set') + var setparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0.category('virtual-machine-os-image-update-parameters') .description($('Commands to set components of virtual-machine-os-image in update-parameters file.')); - setparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0.command('virtual-machine-os-image-update-parameters') + setparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters0.command('set') .description($('Set virtual-machine-os-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":null,\r\n "label":"",\r\n "language":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51725,9 +51725,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1 = catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var removeparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1.category('remove') + var removeparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1.category('virtual-machine-os-image-update-parameters') .description($('Commands to remove components of virtual-machine-os-image in update-parameters file.')); - removeparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1.command('virtual-machine-os-image-update-parameters') + removeparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters1.command('remove') .description($('Remove virtual-machine-os-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":null,\r\n "label":"",\r\n "language":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -51824,9 +51824,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-os-image'); var parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2 = catparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-os-image in the parameter file.')); - var addparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2.category('add') + var addparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2 = parametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2.category('virtual-machine-os-image-update-parameters') .description($('Commands to add components of virtual-machine-os-image in update-parameters file.')); - addparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2.command('virtual-machine-os-image-update-parameters') + addparametersUpdateVirtualMachineOSImageVirtualMachineOSImageUpdateParameters2.command('add') .description($('Add virtual-machine-os-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "isPremium":null,\r\n "label":"",\r\n "language":"",\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52122,9 +52122,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0 = catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0.category('set') + var setparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0.category('virtual-machine-vm-image-create-parameters') .description($('Commands to set components of virtual-machine-vm-image in create-parameters file.')); - setparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0.command('virtual-machine-vm-image-create-parameters') + setparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters0.command('set') .description($('Set virtual-machine-vm-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "name":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52314,9 +52314,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1 = catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1.category('remove') + var removeparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1.category('virtual-machine-vm-image-create-parameters') .description($('Commands to remove components of virtual-machine-vm-image in create-parameters file.')); - removeparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1.command('virtual-machine-vm-image-create-parameters') + removeparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters1.command('remove') .description($('Remove virtual-machine-vm-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "name":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52423,9 +52423,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2 = catparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2.category('add') + var addparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2 = parametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2.category('virtual-machine-vm-image-create-parameters') .description($('Commands to add components of virtual-machine-vm-image in create-parameters file.')); - addparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2.command('virtual-machine-vm-image-create-parameters') + addparametersCreateVirtualMachineVMImageVirtualMachineVMImageCreateParameters2.command('add') .description($('Add virtual-machine-vm-image-create-parameters in create-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "name":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52619,9 +52619,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageDataDiskConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageDataDiskConfigurations0 = catparametersCreateVirtualMachineVMImageDataDiskConfigurations0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersCreateVirtualMachineVMImageDataDiskConfigurations0 = parametersCreateVirtualMachineVMImageDataDiskConfigurations0.category('set') + var setparametersCreateVirtualMachineVMImageDataDiskConfigurations0 = parametersCreateVirtualMachineVMImageDataDiskConfigurations0.category('data-disk-configurations') .description($('Commands to set components of virtual-machine-vm-image in create-parameters file.')); - setparametersCreateVirtualMachineVMImageDataDiskConfigurations0.command('data-disk-configurations') + setparametersCreateVirtualMachineVMImageDataDiskConfigurations0.command('set') .description($('Set data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52694,9 +52694,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageDataDiskConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageDataDiskConfigurations1 = catparametersCreateVirtualMachineVMImageDataDiskConfigurations1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersCreateVirtualMachineVMImageDataDiskConfigurations1 = parametersCreateVirtualMachineVMImageDataDiskConfigurations1.category('remove') + var removeparametersCreateVirtualMachineVMImageDataDiskConfigurations1 = parametersCreateVirtualMachineVMImageDataDiskConfigurations1.category('data-disk-configurations') .description($('Commands to remove components of virtual-machine-vm-image in create-parameters file.')); - removeparametersCreateVirtualMachineVMImageDataDiskConfigurations1.command('data-disk-configurations') + removeparametersCreateVirtualMachineVMImageDataDiskConfigurations1.command('remove') .description($('Remove data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52749,9 +52749,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageDataDiskConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageDataDiskConfigurations2 = catparametersCreateVirtualMachineVMImageDataDiskConfigurations2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersCreateVirtualMachineVMImageDataDiskConfigurations2 = parametersCreateVirtualMachineVMImageDataDiskConfigurations2.category('add') + var addparametersCreateVirtualMachineVMImageDataDiskConfigurations2 = parametersCreateVirtualMachineVMImageDataDiskConfigurations2.category('data-disk-configurations') .description($('Commands to add components of virtual-machine-vm-image in create-parameters file.')); - addparametersCreateVirtualMachineVMImageDataDiskConfigurations2.command('data-disk-configurations') + addparametersCreateVirtualMachineVMImageDataDiskConfigurations2.command('add') .description($('Add data-disk-configurations in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "mediaLink":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52823,9 +52823,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageOSDiskConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageOSDiskConfiguration0 = catparametersCreateVirtualMachineVMImageOSDiskConfiguration0.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersCreateVirtualMachineVMImageOSDiskConfiguration0 = parametersCreateVirtualMachineVMImageOSDiskConfiguration0.category('set') + var setparametersCreateVirtualMachineVMImageOSDiskConfiguration0 = parametersCreateVirtualMachineVMImageOSDiskConfiguration0.category('os-disk-configuration') .description($('Commands to set components of virtual-machine-vm-image in create-parameters file.')); - setparametersCreateVirtualMachineVMImageOSDiskConfiguration0.command('os-disk-configuration') + setparametersCreateVirtualMachineVMImageOSDiskConfiguration0.command('set') .description($('Set os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52904,9 +52904,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageOSDiskConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageOSDiskConfiguration1 = catparametersCreateVirtualMachineVMImageOSDiskConfiguration1.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersCreateVirtualMachineVMImageOSDiskConfiguration1 = parametersCreateVirtualMachineVMImageOSDiskConfiguration1.category('remove') + var removeparametersCreateVirtualMachineVMImageOSDiskConfiguration1 = parametersCreateVirtualMachineVMImageOSDiskConfiguration1.category('os-disk-configuration') .description($('Commands to remove components of virtual-machine-vm-image in create-parameters file.')); - removeparametersCreateVirtualMachineVMImageOSDiskConfiguration1.command('os-disk-configuration') + removeparametersCreateVirtualMachineVMImageOSDiskConfiguration1.command('remove') .description($('Remove os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -52963,9 +52963,9 @@ exports.init = function (cli) { var catparametersCreateVirtualMachineVMImageOSDiskConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersCreateVirtualMachineVMImageOSDiskConfiguration2 = catparametersCreateVirtualMachineVMImageOSDiskConfiguration2.category('create-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersCreateVirtualMachineVMImageOSDiskConfiguration2 = parametersCreateVirtualMachineVMImageOSDiskConfiguration2.category('add') + var addparametersCreateVirtualMachineVMImageOSDiskConfiguration2 = parametersCreateVirtualMachineVMImageOSDiskConfiguration2.category('os-disk-configuration') .description($('Commands to add components of virtual-machine-vm-image in create-parameters file.')); - addparametersCreateVirtualMachineVMImageOSDiskConfiguration2.command('os-disk-configuration') + addparametersCreateVirtualMachineVMImageOSDiskConfiguration2.command('add') .description($('Add os-disk-configuration in create-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":"",\r\n "mediaLink":"",\r\n "oS":"",\r\n "oSState":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53248,9 +53248,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0 = catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0.category('set') + var setparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0.category('virtual-machine-vm-image-replicate-parameters') .description($('Commands to set components of virtual-machine-vm-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0.command('virtual-machine-vm-image-replicate-parameters') + setparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters0.command('set') .description($('Set virtual-machine-vm-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53318,9 +53318,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1 = catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1.category('remove') + var removeparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1.category('virtual-machine-vm-image-replicate-parameters') .description($('Commands to remove components of virtual-machine-vm-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1.command('virtual-machine-vm-image-replicate-parameters') + removeparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters1.command('remove') .description($('Remove virtual-machine-vm-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53372,9 +53372,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2 = catparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2.category('add') + var addparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2 = parametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2.category('virtual-machine-vm-image-replicate-parameters') .description($('Commands to add components of virtual-machine-vm-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2.command('virtual-machine-vm-image-replicate-parameters') + addparametersReplicateVirtualMachineVMImageVirtualMachineVMImageReplicateParameters2.command('add') .description($('Add virtual-machine-vm-image-replicate-parameters in replicate-parameters string or files, e.g. \r\n{\r\n "computeImageAttributes":{\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n },\r\n "marketplaceImageAttributes":{\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n },\r\n "targetLocations":[\r\n ""\r\n ]\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53446,9 +53446,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageComputeImageAttributes0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageComputeImageAttributes0 = catparametersReplicateVirtualMachineVMImageComputeImageAttributes0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersReplicateVirtualMachineVMImageComputeImageAttributes0 = parametersReplicateVirtualMachineVMImageComputeImageAttributes0.category('set') + var setparametersReplicateVirtualMachineVMImageComputeImageAttributes0 = parametersReplicateVirtualMachineVMImageComputeImageAttributes0.category('compute-image-attributes') .description($('Commands to set components of virtual-machine-vm-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineVMImageComputeImageAttributes0.command('compute-image-attributes') + setparametersReplicateVirtualMachineVMImageComputeImageAttributes0.command('set') .description($('Set compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53516,9 +53516,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageComputeImageAttributes1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageComputeImageAttributes1 = catparametersReplicateVirtualMachineVMImageComputeImageAttributes1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersReplicateVirtualMachineVMImageComputeImageAttributes1 = parametersReplicateVirtualMachineVMImageComputeImageAttributes1.category('remove') + var removeparametersReplicateVirtualMachineVMImageComputeImageAttributes1 = parametersReplicateVirtualMachineVMImageComputeImageAttributes1.category('compute-image-attributes') .description($('Commands to remove components of virtual-machine-vm-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineVMImageComputeImageAttributes1.command('compute-image-attributes') + removeparametersReplicateVirtualMachineVMImageComputeImageAttributes1.command('remove') .description($('Remove compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53570,9 +53570,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageComputeImageAttributes2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageComputeImageAttributes2 = catparametersReplicateVirtualMachineVMImageComputeImageAttributes2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersReplicateVirtualMachineVMImageComputeImageAttributes2 = parametersReplicateVirtualMachineVMImageComputeImageAttributes2.category('add') + var addparametersReplicateVirtualMachineVMImageComputeImageAttributes2 = parametersReplicateVirtualMachineVMImageComputeImageAttributes2.category('compute-image-attributes') .description($('Commands to add components of virtual-machine-vm-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineVMImageComputeImageAttributes2.command('compute-image-attributes') + addparametersReplicateVirtualMachineVMImageComputeImageAttributes2.command('add') .description($('Add compute-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "computeImageAttributes" : {\r\n "offer":"",\r\n "sku":"",\r\n "version":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53644,9 +53644,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0 = catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0.category('set') + var setparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0.category('marketplace-image-attributes') .description($('Commands to set components of virtual-machine-vm-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0.command('marketplace-image-attributes') + setparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes0.command('set') .description($('Set marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53703,9 +53703,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1 = catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1.category('remove') + var removeparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1.category('marketplace-image-attributes') .description($('Commands to remove components of virtual-machine-vm-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1.command('marketplace-image-attributes') + removeparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes1.command('remove') .description($('Remove marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53752,9 +53752,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2 = catparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2.category('add') + var addparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2 = parametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2.category('marketplace-image-attributes') .description($('Commands to add components of virtual-machine-vm-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2.command('marketplace-image-attributes') + addparametersReplicateVirtualMachineVMImageMarketplaceImageAttributes2.command('add') .description($('Add marketplace-image-attributes in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "marketplaceImageAttributes" : {\r\n "plan":{\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n },\r\n "publisherId":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53815,9 +53815,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImagePlan0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImagePlan0 = catparametersReplicateVirtualMachineVMImagePlan0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersReplicateVirtualMachineVMImagePlan0 = parametersReplicateVirtualMachineVMImagePlan0.category('set') + var setparametersReplicateVirtualMachineVMImagePlan0 = parametersReplicateVirtualMachineVMImagePlan0.category('plan') .description($('Commands to set components of virtual-machine-vm-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineVMImagePlan0.command('plan') + setparametersReplicateVirtualMachineVMImagePlan0.command('set') .description($('Set plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53885,9 +53885,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImagePlan1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImagePlan1 = catparametersReplicateVirtualMachineVMImagePlan1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersReplicateVirtualMachineVMImagePlan1 = parametersReplicateVirtualMachineVMImagePlan1.category('remove') + var removeparametersReplicateVirtualMachineVMImagePlan1 = parametersReplicateVirtualMachineVMImagePlan1.category('plan') .description($('Commands to remove components of virtual-machine-vm-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineVMImagePlan1.command('plan') + removeparametersReplicateVirtualMachineVMImagePlan1.command('remove') .description($('Remove plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -53939,9 +53939,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImagePlan2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImagePlan2 = catparametersReplicateVirtualMachineVMImagePlan2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersReplicateVirtualMachineVMImagePlan2 = parametersReplicateVirtualMachineVMImagePlan2.category('add') + var addparametersReplicateVirtualMachineVMImagePlan2 = parametersReplicateVirtualMachineVMImagePlan2.category('plan') .description($('Commands to add components of virtual-machine-vm-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineVMImagePlan2.command('plan') + addparametersReplicateVirtualMachineVMImagePlan2.command('add') .description($('Add plan in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "plan" : {\r\n "name":"",\r\n "product":"",\r\n "publisher":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54013,9 +54013,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageTargetLocations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageTargetLocations0 = catparametersReplicateVirtualMachineVMImageTargetLocations0.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersReplicateVirtualMachineVMImageTargetLocations0 = parametersReplicateVirtualMachineVMImageTargetLocations0.category('set') + var setparametersReplicateVirtualMachineVMImageTargetLocations0 = parametersReplicateVirtualMachineVMImageTargetLocations0.category('target-locations') .description($('Commands to set components of virtual-machine-vm-image in replicate-parameters file.')); - setparametersReplicateVirtualMachineVMImageTargetLocations0.command('target-locations') + setparametersReplicateVirtualMachineVMImageTargetLocations0.command('set') .description($('Set target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54055,9 +54055,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageTargetLocations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageTargetLocations1 = catparametersReplicateVirtualMachineVMImageTargetLocations1.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersReplicateVirtualMachineVMImageTargetLocations1 = parametersReplicateVirtualMachineVMImageTargetLocations1.category('remove') + var removeparametersReplicateVirtualMachineVMImageTargetLocations1 = parametersReplicateVirtualMachineVMImageTargetLocations1.category('target-locations') .description($('Commands to remove components of virtual-machine-vm-image in replicate-parameters file.')); - removeparametersReplicateVirtualMachineVMImageTargetLocations1.command('target-locations') + removeparametersReplicateVirtualMachineVMImageTargetLocations1.command('remove') .description($('Remove target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54089,9 +54089,9 @@ exports.init = function (cli) { var catparametersReplicateVirtualMachineVMImageTargetLocations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersReplicateVirtualMachineVMImageTargetLocations2 = catparametersReplicateVirtualMachineVMImageTargetLocations2.category('replicate-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersReplicateVirtualMachineVMImageTargetLocations2 = parametersReplicateVirtualMachineVMImageTargetLocations2.category('add') + var addparametersReplicateVirtualMachineVMImageTargetLocations2 = parametersReplicateVirtualMachineVMImageTargetLocations2.category('target-locations') .description($('Commands to add components of virtual-machine-vm-image in replicate-parameters file.')); - addparametersReplicateVirtualMachineVMImageTargetLocations2.command('target-locations') + addparametersReplicateVirtualMachineVMImageTargetLocations2.command('add') .description($('Add target-locations in replicate-parameters string or files, e.g. \r\n {\r\n ...\r\n "targetLocations" : ""\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54313,9 +54313,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0 = catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0.category('set') + var setparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0.category('virtual-machine-vm-image-update-parameters') .description($('Commands to set components of virtual-machine-vm-image in update-parameters file.')); - setparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0.command('virtual-machine-vm-image-update-parameters') + setparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters0.command('set') .description($('Set virtual-machine-vm-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54494,9 +54494,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1 = catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1.category('remove') + var removeparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1.category('virtual-machine-vm-image-update-parameters') .description($('Commands to remove components of virtual-machine-vm-image in update-parameters file.')); - removeparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1.command('virtual-machine-vm-image-update-parameters') + removeparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters1.command('remove') .description($('Remove virtual-machine-vm-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54598,9 +54598,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2 = catparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2.category('add') + var addparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2 = parametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2.category('virtual-machine-vm-image-update-parameters') .description($('Commands to add components of virtual-machine-vm-image in update-parameters file.')); - addparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2.command('virtual-machine-vm-image-update-parameters') + addparametersUpdateVirtualMachineVMImageVirtualMachineVMImageUpdateParameters2.command('add') .description($('Add virtual-machine-vm-image-update-parameters in update-parameters string or files, e.g. \r\n{\r\n "dataDiskConfigurations":[\r\n {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ],\r\n "description":"",\r\n "eula":"",\r\n "iconUri":"",\r\n "imageFamily":"",\r\n "label":"",\r\n "language":"",\r\n "oSDiskConfiguration":{\r\n "hostCaching":""\r\n },\r\n "privacyUri":"",\r\n "publishedDate":null,\r\n "recommendedVMSize":"",\r\n "showInGui":null,\r\n "smallIconUri":""\r\n}\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54783,9 +54783,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageDataDiskConfigurations0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageDataDiskConfigurations0 = catparametersUpdateVirtualMachineVMImageDataDiskConfigurations0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersUpdateVirtualMachineVMImageDataDiskConfigurations0 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations0.category('set') + var setparametersUpdateVirtualMachineVMImageDataDiskConfigurations0 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations0.category('data-disk-configurations') .description($('Commands to set components of virtual-machine-vm-image in update-parameters file.')); - setparametersUpdateVirtualMachineVMImageDataDiskConfigurations0.command('data-disk-configurations') + setparametersUpdateVirtualMachineVMImageDataDiskConfigurations0.command('set') .description($('Set data-disk-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54858,9 +54858,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageDataDiskConfigurations1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageDataDiskConfigurations1 = catparametersUpdateVirtualMachineVMImageDataDiskConfigurations1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersUpdateVirtualMachineVMImageDataDiskConfigurations1 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations1.category('remove') + var removeparametersUpdateVirtualMachineVMImageDataDiskConfigurations1 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations1.category('data-disk-configurations') .description($('Commands to remove components of virtual-machine-vm-image in update-parameters file.')); - removeparametersUpdateVirtualMachineVMImageDataDiskConfigurations1.command('data-disk-configurations') + removeparametersUpdateVirtualMachineVMImageDataDiskConfigurations1.command('remove') .description($('Remove data-disk-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54913,9 +54913,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageDataDiskConfigurations2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageDataDiskConfigurations2 = catparametersUpdateVirtualMachineVMImageDataDiskConfigurations2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersUpdateVirtualMachineVMImageDataDiskConfigurations2 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations2.category('add') + var addparametersUpdateVirtualMachineVMImageDataDiskConfigurations2 = parametersUpdateVirtualMachineVMImageDataDiskConfigurations2.category('data-disk-configurations') .description($('Commands to add components of virtual-machine-vm-image in update-parameters file.')); - addparametersUpdateVirtualMachineVMImageDataDiskConfigurations2.command('data-disk-configurations') + addparametersUpdateVirtualMachineVMImageDataDiskConfigurations2.command('add') .description($('Add data-disk-configurations in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "dataDiskConfigurations" : {\r\n "hostCaching":"",\r\n "logicalUnitNumber":null,\r\n "name":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -54987,9 +54987,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageOSDiskConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageOSDiskConfiguration0 = catparametersUpdateVirtualMachineVMImageOSDiskConfiguration0.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var setparametersUpdateVirtualMachineVMImageOSDiskConfiguration0 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration0.category('set') + var setparametersUpdateVirtualMachineVMImageOSDiskConfiguration0 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration0.category('os-disk-configuration') .description($('Commands to set components of virtual-machine-vm-image in update-parameters file.')); - setparametersUpdateVirtualMachineVMImageOSDiskConfiguration0.command('os-disk-configuration') + setparametersUpdateVirtualMachineVMImageOSDiskConfiguration0.command('set') .description($('Set os-disk-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -55035,9 +55035,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageOSDiskConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageOSDiskConfiguration1 = catparametersUpdateVirtualMachineVMImageOSDiskConfiguration1.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var removeparametersUpdateVirtualMachineVMImageOSDiskConfiguration1 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration1.category('remove') + var removeparametersUpdateVirtualMachineVMImageOSDiskConfiguration1 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration1.category('os-disk-configuration') .description($('Commands to remove components of virtual-machine-vm-image in update-parameters file.')); - removeparametersUpdateVirtualMachineVMImageOSDiskConfiguration1.command('os-disk-configuration') + removeparametersUpdateVirtualMachineVMImageOSDiskConfiguration1.command('remove') .description($('Remove os-disk-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) @@ -55079,9 +55079,9 @@ exports.init = function (cli) { var catparametersUpdateVirtualMachineVMImageOSDiskConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('virtual-machine-vm-image'); var parametersUpdateVirtualMachineVMImageOSDiskConfiguration2 = catparametersUpdateVirtualMachineVMImageOSDiskConfiguration2.category('update-parameters') .description($('Commands to manage configuration of virtual-machine-vm-image in the parameter file.')); - var addparametersUpdateVirtualMachineVMImageOSDiskConfiguration2 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration2.category('add') + var addparametersUpdateVirtualMachineVMImageOSDiskConfiguration2 = parametersUpdateVirtualMachineVMImageOSDiskConfiguration2.category('os-disk-configuration') .description($('Commands to add components of virtual-machine-vm-image in update-parameters file.')); - addparametersUpdateVirtualMachineVMImageOSDiskConfiguration2.command('os-disk-configuration') + addparametersUpdateVirtualMachineVMImageOSDiskConfiguration2.command('add') .description($('Add os-disk-configuration in update-parameters string or files, e.g. \r\n {\r\n ...\r\n "oSDiskConfiguration" : {\r\n "hostCaching":""\r\n }\r\n ...\r\n }\r\n\r\n There are two sets of commands:\r\n 1) function commands that are used to manage Azure resources in the cloud, and \r\n 2) parameter commands that generate & edit input files for the other set of commands.\r\n For example, \'vmss get/list/stop\' are the function commands that call get, list and stop operations of \r\n virtual machine scale set, whereas \'vmss config * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) .usage('[options]') .option('--parameter-file ', $('The parameter file path.')) diff --git a/tools/StaticAnalysis/AnalysisLogger.cs b/tools/StaticAnalysis/AnalysisLogger.cs index f6aa7b493f3e..f1a4eb91f77d 100644 --- a/tools/StaticAnalysis/AnalysisLogger.cs +++ b/tools/StaticAnalysis/AnalysisLogger.cs @@ -26,14 +26,27 @@ namespace StaticAnalysis public abstract class AnalysisLogger { string _baseDirectory; + string _exceptionsDirectory; /// /// Create an analysis logger that will write reports to the given directory /// - /// + /// The base directory for reports + /// The directory containing exceptions form static analysis rules. + public AnalysisLogger(string baseDirectory, string exceptionsDirectory) + { + _baseDirectory = baseDirectory; + _exceptionsDirectory = exceptionsDirectory; + } + + /// + /// Create an analysis logger without exceptions + /// + /// The base directory for reports public AnalysisLogger(string baseDirectory) { _baseDirectory = baseDirectory; + _exceptionsDirectory = null; } IList _loggers = new List(); @@ -86,7 +99,7 @@ public virtual void WriteWarning(string format, params object[] args) /// The filename (without file path) where the report will be written /// The given logger. Analyzer may write records to this logger and they will be written to /// the report file. - public virtual ReportLogger CreateLogger(string fileName) where T : IReportRecord, new() + public virtual ReportLogger CreateLogger(string fileName) where T : class, IReportRecord, new() { if (string.IsNullOrWhiteSpace(fileName)) { @@ -94,7 +107,19 @@ public virtual void WriteWarning(string format, params object[] args) } var filePath = Path.Combine(_baseDirectory, fileName); - var logger = new ReportLogger(filePath, this); + ReportLogger logger; + if (_exceptionsDirectory != null && Directory.Exists(_exceptionsDirectory)) + { + var exceptionsPath = Path.Combine(_exceptionsDirectory, fileName); + WriteWarning("Using exceptions file {0}", exceptionsPath); + logger = new ReportLogger(filePath, exceptionsPath, this); + } + else + { + WriteWarning("Using no exceptions file."); + logger = new ReportLogger(filePath, this); + } + Loggers.Add(logger); return logger; } @@ -116,5 +141,31 @@ public void WriteReports() WriteReport(logger.FileName, reportText.ToString()); } } + + public void CheckForIssues(int maxSeverity) + { + var hasErrors = false; + foreach (var logger in Loggers.Where(l => l.Records.Any(r => r.Severity < maxSeverity))) + { + hasErrors = true; + StringBuilder errorText = new StringBuilder(); + errorText.AppendLine(logger.Records.First().PrintHeaders()); + foreach (var reportRecord in logger.Records) + { + errorText.AppendLine(reportRecord.FormatRecord()); + } + + WriteError("{0} Errors", logger.FileName); + WriteError(errorText.ToString()); + WriteError(""); + } + + if (hasErrors) + { + throw new InvalidOperationException(string.Format("One or more errors occurred in validation. " + + "See the analysis repots at {0} for details", + _baseDirectory)); + } + } } } diff --git a/tools/StaticAnalysis/ConsoleLogger.cs b/tools/StaticAnalysis/ConsoleLogger.cs index 1cb18d070d64..22a3b73fa90f 100644 --- a/tools/StaticAnalysis/ConsoleLogger.cs +++ b/tools/StaticAnalysis/ConsoleLogger.cs @@ -23,11 +23,15 @@ namespace StaticAnalysis public class ConsoleLogger : AnalysisLogger { + public ConsoleLogger(string baseDirectory, string exceptionsDirectory) + : base(baseDirectory, exceptionsDirectory) + { + } + public ConsoleLogger(string baseDirectory) : base(baseDirectory) { } - public override void WriteError(string error) { Console.WriteLine("### ERROR {0}", error); diff --git a/tools/StaticAnalysis/DependencyAnalyzer/AssemblyRecord.cs b/tools/StaticAnalysis/DependencyAnalyzer/AssemblyRecord.cs index a6a0c41e9e53..90e04d3adcd6 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/AssemblyRecord.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/AssemblyRecord.cs @@ -114,6 +114,12 @@ public override string ToString() } + public override int GetHashCode() + { + return string.Format("{0}-{1}-{2}", AssemblyName, AssemblyFileMajorVersion, AssemblyFileMinorVersion).GetHashCode(); + } + + /// /// Get all the ancestors in the ancestor tree /// diff --git a/tools/StaticAnalysis/DependencyAnalyzer/AssemblyVersionConflict.cs b/tools/StaticAnalysis/DependencyAnalyzer/AssemblyVersionConflict.cs index 7c54d20f5571..b2750f981c42 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/AssemblyVersionConflict.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/AssemblyVersionConflict.cs @@ -13,6 +13,8 @@ // ---------------------------------------------------------------------------------- using System; +using System.IO; +using System.Text.RegularExpressions; namespace StaticAnalysis.DependencyAnalyzer { @@ -46,6 +48,11 @@ public class AssemblyVersionConflict : IReportRecord /// public string ParentAssembly { get; set; } + /// + /// Machine readable identity of the problem + /// + public int ProblemId { get; set; } + /// /// A textual description of the problem /// @@ -62,16 +69,52 @@ public string PrintHeaders() { return "\"Directory\",\"AssemblyName\",\"Expected Version\",\"Actual Version\",\"Parent Assembly\",\"Severity\"," + - "\"Description\",\"Remediation\""; + "\"ProblemId\",\"Description\",\"Remediation\""; } public string FormatRecord() { return string.Format( - "\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\",\"{7}\"", + "\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\",\"{7}\",\"{8}\"", Directory, AssemblyName, ExpectedVersion, ActualVersion, ParentAssembly, Severity, - Description, Remediation); + ProblemId, Description, Remediation); + } + public bool Match(IReportRecord other) + { + var result = false; + var record = other as AssemblyVersionConflict; + if (record != null) + { + result = string.Equals(EnvironmentHelpers.GetDirectoryName(record.Directory), + EnvironmentHelpers.GetDirectoryName(Directory), StringComparison.OrdinalIgnoreCase) + && string.Equals(record.AssemblyName, AssemblyName, StringComparison.OrdinalIgnoreCase) + && string.Equals(record.ParentAssembly, ParentAssembly, StringComparison.OrdinalIgnoreCase) + &&record.ProblemId == ProblemId; + } + + return result; + } + + public IReportRecord Parse(string line) + { + var matcher = "\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\""; + var match = Regex.Match(line, matcher); + if (!match.Success || match.Groups.Count < 10) + { + throw new InvalidOperationException(string.Format("Could not parse '{0}' as AssemblyVersionConflict record", line)); + } + + Directory = match.Groups[1].Value; + AssemblyName = match.Groups[2].Value; + ExpectedVersion = Version.Parse(match.Groups[3].Value); + ActualVersion = Version.Parse(match.Groups[4].Value); + ParentAssembly = match.Groups[5].Value; + Severity = int.Parse(match.Groups[6].Value); + ProblemId = int.Parse(match.Groups[7].Value); + Description = match.Groups[8].Value; + Remediation = match.Groups[9].Value; + return this; } public override string ToString() diff --git a/tools/StaticAnalysis/DependencyAnalyzer/DependencyAnalyzer.cs b/tools/StaticAnalysis/DependencyAnalyzer/DependencyAnalyzer.cs index 62f8ee2786ff..b79bec67f05b 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/DependencyAnalyzer.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/DependencyAnalyzer.cs @@ -13,6 +13,7 @@ // ---------------------------------------------------------------------------------- using System; +using System.CodeDom; using System.Collections.Generic; using System.Diagnostics; using System.IO; @@ -26,6 +27,21 @@ namespace StaticAnalysis.DependencyAnalyzer /// public class DependencyAnalyzer : IStaticAnalyzer { + const int NoAssemblyVersionEvidence = 1000; + const int ReferenceDoesNotMatchAssemblyVersion = 1010; + const int ExtraAssemblyRecord = 2000; + const int MissingAssemblyRecord = 3000; + const int AssemblyVersionFileVersionMismatch = 7000; + const int CommonAuthenticationMismatch = 7010; + + static List FrameworkAssemblies = new List + { + "Microsoft.CSharp", + "Microsoft.Management.Infrastructure", + "Microsoft.Build", + "Microsoft.Build.Framework" + }; + private Dictionary _assemblies = new Dictionary(StringComparer.OrdinalIgnoreCase); private Dictionary _sharedAssemblyReferences = @@ -130,6 +146,7 @@ private bool AddSharedAssembly(AssemblyRecord assembly) }, AssemblyVersion = assembly.Version, Severity = 0, + ProblemId = AssemblyVersionFileVersionMismatch, Description = "Shared assembly conflict, shared assemblies with the same assembly " + "version have differing file versions", Remediation = string.Format("Update the assembly reference for {0} in one of the " + @@ -170,6 +187,7 @@ private bool AddSharedAssemblyExactVersion(AssemblyRecord record) AssemblyName = record.Name, AssemblyVersion = record.Version, Severity = 0, + ProblemId = CommonAuthenticationMismatch, AssemblyPathsAndFileVersions = new List>() { new Tuple(record.Location, new Version(record.AssemblyFileMajorVersion, @@ -202,14 +220,15 @@ private static bool RequiresExactVersionMatch(AssemblyRecord name) private static bool IsFrameworkAssembly(AssemblyName name) { - return name.Name.StartsWith("System") || name.Name.Equals("mscorlib"); + return name.Name.StartsWith("System") || name.Name.Equals("mscorlib") + || FrameworkAssemblies.Contains(name.Name); } private void ProcessDirectory(string directoryPath) { var savedDirectory = Directory.GetCurrentDirectory(); Directory.SetCurrentDirectory(directoryPath); - _loader = AppDomainHelpers.CreateProxy(directoryPath, out _testDomain); + _loader = EnvironmentHelpers.CreateProxy(directoryPath, out _testDomain); foreach (var file in Directory.GetFiles(directoryPath).Where(file => file.EndsWith(".dll"))) { AssemblyRecord assembly = CreateAssemblyRecord(file); @@ -258,6 +277,7 @@ var assembly in { AssemblyName = assembly.Name, Severity = 2, + ProblemId = ExtraAssemblyRecord, Description = string.Format("Assembly {0} is not referenced from any cmdlets assembly", assembly.Name), Remediation = string.Format("Remove assembly {0} from the project and regenerate the Wix " + @@ -286,6 +306,7 @@ private void CheckAssemblyReference(AssemblyName reference, AssemblyRecord paren ActualVersion = stored.Version, ExpectedVersion = reference.Version, ParentAssembly = parent.Name, + ProblemId = NoAssemblyVersionEvidence, Severity = 2, Description = string.Format("Assembly {0} referenced from {1}.dll does not specify any " + "assembly version evidence. The assembly will use version " + @@ -304,6 +325,7 @@ private void CheckAssemblyReference(AssemblyName reference, AssemblyRecord paren ActualVersion = stored.Version, ExpectedVersion = reference.Version, ParentAssembly = parent.Name, + ProblemId = ReferenceDoesNotMatchAssemblyVersion, Severity = 1, Description = string.Format("Assembly {0} version {1} referenced from {2}.dll does " + "not match assembly version on disk: {3}", @@ -321,6 +343,7 @@ private void CheckAssemblyReference(AssemblyName reference, AssemblyRecord paren AssemblyVersion = reference.Version.ToString(), ReferencingAssembly = parent.Name, Severity = 0, + ProblemId = MissingAssemblyRecord, Description = string.Format("Missing assembly {0} referenced from {1}", reference.Name, parent.Name), Remediation = "Ensure that the assembly is included in the Wix file or directory" diff --git a/tools/StaticAnalysis/DependencyAnalyzer/ExtraAssembly.cs b/tools/StaticAnalysis/DependencyAnalyzer/ExtraAssembly.cs index 677bb9271054..5b0a4b07b14b 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/ExtraAssembly.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/ExtraAssembly.cs @@ -12,6 +12,9 @@ // limitations under the License. // ---------------------------------------------------------------------------------- +using System; +using System.Text.RegularExpressions; + namespace StaticAnalysis.DependencyAnalyzer { /// @@ -25,6 +28,8 @@ public class ExtraAssembly : IReportRecord public int Severity { get; set; } + public int ProblemId { get; set; } + public string Description { get; set; } public string Remediation { get; set; } @@ -32,18 +37,52 @@ public class ExtraAssembly : IReportRecord public string PrintHeaders() { - return "\"Directory\",\"AssemblyName\",\"Severity\",\"Description\",\"Remediation\""; + return "\"Directory\",\"AssemblyName\",\"Severity\",\"ProblemId\",\"Description\",\"Remediation\""; } public string FormatRecord() { - return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\"", - Directory, AssemblyName, Severity, Description, Remediation); + return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\"", + Directory, AssemblyName, Severity, ProblemId, Description, Remediation); } public override string ToString() { return FormatRecord(); } + + + public bool Match(IReportRecord other) + { + var result = false; + var record = other as ExtraAssembly; + if (record != null) + { + result = string.Equals(EnvironmentHelpers.GetDirectoryName(record.Directory), + EnvironmentHelpers.GetDirectoryName(Directory), StringComparison.OrdinalIgnoreCase) + && string.Equals(record.AssemblyName, AssemblyName, StringComparison.OrdinalIgnoreCase) + && record.ProblemId == ProblemId; + } + + return result; + } + + public IReportRecord Parse(string line) + { + var matcher = "\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\""; + var match = Regex.Match(line, matcher); + if (!match.Success || match.Groups.Count < 7) + { + throw new InvalidOperationException(string.Format("Could not parse '{0}' as ExtraAssembly record", line)); + } + + Directory = match.Groups[1].Value; + AssemblyName = match.Groups[2].Value; + Severity = int.Parse(match.Groups[3].Value); + ProblemId = int.Parse(match.Groups[4].Value); + Description = match.Groups[5].Value; + Remediation = match.Groups[6].Value; + return this; + } } } diff --git a/tools/StaticAnalysis/DependencyAnalyzer/MissingAssembly.cs b/tools/StaticAnalysis/DependencyAnalyzer/MissingAssembly.cs index ea73fd482404..89b4a8000970 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/MissingAssembly.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/MissingAssembly.cs @@ -12,6 +12,9 @@ // limitations under the License. // ---------------------------------------------------------------------------------- +using System; +using System.Text.RegularExpressions; + namespace StaticAnalysis.DependencyAnalyzer { /// @@ -23,6 +26,7 @@ public class MissingAssembly : IReportRecord public string AssemblyName { get; set; } public string AssemblyVersion { get; set; } public string ReferencingAssembly { get; set; } + public int ProblemId { get; set; } public string Description { get; set; } public string Remediation { get; set; } public int Severity { get; set; } @@ -30,14 +34,51 @@ public class MissingAssembly : IReportRecord public string PrintHeaders() { return "\"Directory\",\"Assembly Name\",\"Assembly Version\",\"Referencing Assembly\"," + - "\"Severity\",\"Description\",\"Remediation\""; + "\"Severity\",\"ProblemId\",\"Description\",\"Remediation\""; } public string FormatRecord() { - return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\"", + return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\",\"{7}\"", Directory, AssemblyName, AssemblyVersion, ReferencingAssembly, - Severity, Description, Remediation); + Severity, ProblemId, Description, Remediation); + } + + public bool Match(IReportRecord other) + { + var result = false; + var record = other as MissingAssembly; + if (record != null) + { + result = string.Equals(EnvironmentHelpers.GetDirectoryName(record.Directory), + EnvironmentHelpers.GetDirectoryName(Directory), StringComparison.OrdinalIgnoreCase) + && string.Equals(record.AssemblyName, AssemblyName, StringComparison.OrdinalIgnoreCase) + && string.Equals(record.AssemblyVersion, AssemblyVersion, StringComparison.OrdinalIgnoreCase) + && string.Equals(record.ReferencingAssembly, ReferencingAssembly, StringComparison.OrdinalIgnoreCase) + && record.ProblemId == ProblemId; + } + + return result; + } + + public IReportRecord Parse(string line) + { + var matcher = "\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\""; + var match = Regex.Match(line, matcher); + if (!match.Success || match.Groups.Count < 9) + { + throw new InvalidOperationException(string.Format("Could not parse '{0}' as MissingAssembly record", line)); + } + + Directory = match.Groups[1].Value; + AssemblyName = match.Groups[2].Value; + AssemblyVersion = match.Groups[3].Value; + ReferencingAssembly = match.Groups[4].Value; + Severity = int.Parse(match.Groups[5].Value); + ProblemId = int.Parse(match.Groups[6].Value); + Description = match.Groups[7].Value; + Remediation = match.Groups[8].Value; + return this; } public override string ToString() diff --git a/tools/StaticAnalysis/DependencyAnalyzer/SharedAssemblyConflict.cs b/tools/StaticAnalysis/DependencyAnalyzer/SharedAssemblyConflict.cs index f2b8b0b9b4e6..fe13e2ceeb86 100644 --- a/tools/StaticAnalysis/DependencyAnalyzer/SharedAssemblyConflict.cs +++ b/tools/StaticAnalysis/DependencyAnalyzer/SharedAssemblyConflict.cs @@ -14,7 +14,9 @@ using System; using System.Collections.Generic; +using System.IO; using System.Linq; +using System.Text.RegularExpressions; namespace StaticAnalysis.DependencyAnalyzer { @@ -27,13 +29,14 @@ public class SharedAssemblyConflict : IReportRecord public string AssemblyName { get; set; } public Version AssemblyVersion { get; set; } public List> AssemblyPathsAndFileVersions { get; set; } + public int ProblemId { get; set; } public string Description { get; set; } public string Remediation { get; set; } public int Severity { get; set; } public string PrintHeaders() { - return "\"Target\",\"AssemblyName\",\"AssemblyVersion\",\"Severity\",\"Description\",\"Remediation\""; + return "\"Target\",\"AssemblyName\",\"AssemblyVersion\",\"Severity\",\"ProblemId\",\"Description\",\"Remediation\""; } public string FormatRecord() @@ -41,8 +44,40 @@ public string FormatRecord() var targets = AssemblyPathsAndFileVersions.Select(s => string.Format("File version {0} in {1}", s.Item2, s.Item1)); var targetString = string.Join(", ", targets); - return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\"", targetString, AssemblyName, - AssemblyVersion, Severity, Description, Remediation); + return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\"", targetString, AssemblyName, + AssemblyVersion, Severity, ProblemId, Description, Remediation); + } + + public bool Match(IReportRecord other) + { + var result = false; + var record = other as SharedAssemblyConflict; + if (record != null) + { + result = string.Equals(record.AssemblyName, AssemblyName, StringComparison.OrdinalIgnoreCase) && + record.AssemblyVersion == AssemblyVersion && + record.ProblemId == ProblemId; + } + + return result; + } + + public IReportRecord Parse(string line) + { + var matcher = "\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\""; + var match = Regex.Match(line, matcher); + if (!match.Success || match.Groups.Count < 8) + { + throw new InvalidOperationException(string.Format("Could not parse '{0}' as SharedAssemblyConflict record", line)); + } + + AssemblyName = match.Groups[2].Value; + AssemblyVersion = Version.Parse(match.Groups[3].Value); + Severity = int.Parse(match.Groups[4].Value); + ProblemId = int.Parse(match.Groups[5].Value); + Description = match.Groups[6].Value; + Remediation = match.Groups[7].Value; + return this; } public override string ToString() diff --git a/tools/StaticAnalysis/AppDomainHelpers.cs b/tools/StaticAnalysis/EnvironmentHelpers.cs similarity index 73% rename from tools/StaticAnalysis/AppDomainHelpers.cs rename to tools/StaticAnalysis/EnvironmentHelpers.cs index cdf32c4cc754..576301c67b38 100644 --- a/tools/StaticAnalysis/AppDomainHelpers.cs +++ b/tools/StaticAnalysis/EnvironmentHelpers.cs @@ -16,7 +16,7 @@ namespace StaticAnalysis { - public static class AppDomainHelpers + public static class EnvironmentHelpers { /// /// Create a new AppDomain and create a remote instance of AssemblyLoader we can use there @@ -26,7 +26,7 @@ public static class AppDomainHelpers /// A proxy to the AssemblyLoader running in the newly created app domain public static T CreateProxy(string directoryPath, out AppDomain testDomain) where T:MarshalByRefObject { - if (string.IsNullOrWhiteSpace(directoryPath)) + if (String.IsNullOrWhiteSpace(directoryPath)) { throw new ArgumentException("directoryPath"); } @@ -43,5 +43,27 @@ public static T CreateProxy(string directoryPath, out AppDomain testDomain) w return testDomain.CreateInstanceFromAndUnwrap(typeof(T).Assembly.Location, typeof(T).FullName) as T; } + + /// + /// Get the name of the directory from a directory path + /// + /// A directory path + /// The name of the directory + public static string GetDirectoryName(string path) + { + if (path == null) + { + throw new ArgumentNullException("path"); + } + + string result = path.TrimEnd('\\'); + var lastSlash = result.LastIndexOf("\\"); + if (lastSlash > 0) + { + result = result.Substring(lastSlash + 1); + } + + return result; + } } } diff --git a/tools/StaticAnalysis/Exceptions/AssemblyVersionConflict.csv b/tools/StaticAnalysis/Exceptions/AssemblyVersionConflict.csv new file mode 100644 index 000000000000..a31380397327 --- /dev/null +++ b/tools/StaticAnalysis/Exceptions/AssemblyVersionConflict.csv @@ -0,0 +1,5 @@ +"Directory","AssemblyName","Expected Version","Actual Version","Parent Assembly","Severity","ProblemId","Description","Remediation" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Data.OData","5.6.2.0","5.6.4.0","Microsoft.Azure.Batch","1","1010","Assembly Microsoft.Data.OData version 5.6.2.0 referenced from Microsoft.Azure.Batch.dll does not match assembly version on disk: 5.6.4.0","Update any references to version 5.6.2.0 of assembly Microsoft.Data.OData" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.WindowsAzure.Storage","4.3.0.0","6.1.0.0","Microsoft.Azure.Batch","1","1010","Assembly Microsoft.WindowsAzure.Storage version 4.3.0.0 referenced from Microsoft.Azure.Batch.dll does not match assembly version on disk: 6.1.0.0","Update any references to version 4.3.0.0 of assembly Microsoft.WindowsAzure.Storage" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.WindowsAzure.Storage","6.0.0.0","6.1.0.0","Microsoft.Azure.Insights","1","1010","Assembly Microsoft.WindowsAzure.Storage version 6.0.0.0 referenced from Microsoft.Azure.Insights.dll does not match assembly version on disk: 6.1.0.0","Update any references to version 6.0.0.0 of assembly Microsoft.WindowsAzure.Storage" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","Microsoft.WindowsAzure.Storage","3.0.3.0","6.0.0.0","Microsoft.Hadoop.Client","1","1010","Assembly Microsoft.WindowsAzure.Storage version 3.0.3.0 referenced from Microsoft.Hadoop.Client.dll does not match assembly version on disk: 6.0.0.0","Update any references to version 3.0.3.0 of assembly Microsoft.WindowsAzure.Storage" diff --git a/tools/StaticAnalysis/Exceptions/ExtraAssemblies.csv b/tools/StaticAnalysis/Exceptions/ExtraAssemblies.csv new file mode 100644 index 000000000000..34242053b703 --- /dev/null +++ b/tools/StaticAnalysis/Exceptions/ExtraAssemblies.csv @@ -0,0 +1,266 @@ +"Directory","AssemblyName","Severity","ProblemId","Description","Remediation" +"src\Package\Debug\ResourceManager\AzureResourceManager\Azure.Storage","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\Azure.Storage","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\Azure.Storage","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\Azure.Storage","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\Azure.Storage","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","AutoMapper.Net4","2","2000","Assembly AutoMapper.Net4 is not referenced from any cmdlets assembly","Remove assembly AutoMapper.Net4 from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.ApiManagement","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Automation","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackAdmin","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackAdmin","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackAdmin","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackStorage","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackStorage","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.AzureStackStorage","Microsoft.WindowsAzure.Configuration","2","2000","Assembly Microsoft.WindowsAzure.Configuration is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Configuration from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Backup","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Azure.KeyVault.Core","2","2000","Assembly Microsoft.Azure.KeyVault.Core is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.KeyVault.Core from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","Microsoft.WindowsAzure.Storage","2","2000","Assembly Microsoft.WindowsAzure.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Batch","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Compute","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataFactories","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeAnalytics","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.DataLakeStore","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","Microsoft.Azure.Management.Authorization","2","2000","Assembly Microsoft.Azure.Management.Authorization is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.Management.Authorization from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Dns","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.HDInsight","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.HDInsight","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.HDInsight","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.HDInsight","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Insights","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Insights","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.KeyVault","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.LogicApp","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.LogicApp","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.LogicApp","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","AutoMapper.Net4","2","2000","Assembly AutoMapper.Net4 is not referenced from any cmdlets assembly","Remove assembly AutoMapper.Net4 from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Azure.KeyVault.Core","2","2000","Assembly Microsoft.Azure.KeyVault.Core is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.KeyVault.Core from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","Microsoft.WindowsAzure.Storage","2","2000","Assembly Microsoft.WindowsAzure.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Network","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.NotificationHubs","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.NotificationHubs","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.NotificationHubs","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.NotificationHubs","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.NotificationHubs","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.OperationalInsights","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Profile","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RecoveryServices","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RecoveryServices","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RecoveryServices","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RecoveryServices","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RecoveryServices","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Azure.KeyVault.Core","2","2000","Assembly Microsoft.Azure.KeyVault.Core is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.KeyVault.Core from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","Microsoft.WindowsAzure.Storage","2","2000","Assembly Microsoft.WindowsAzure.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.RedisCache","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Resources","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.SiteRecovery","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.SiteRecovery","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.SiteRecovery","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.SiteRecovery","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.SiteRecovery","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.Azure.KeyVault.Core","2","2000","Assembly Microsoft.Azure.KeyVault.Core is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.KeyVault.Core from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","Microsoft.WindowsAzure.Storage","2","2000","Assembly Microsoft.WindowsAzure.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Sql","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Storage","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Storage","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Storage","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Storage","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Storage","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.Azure.KeyVault.Core","2","2000","Assembly Microsoft.Azure.KeyVault.Core is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.KeyVault.Core from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.Azure.ResourceManager","2","2000","Assembly Microsoft.Azure.ResourceManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.Azure.ResourceManager from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","Microsoft.WindowsAzure.Storage","2","2000","Assembly Microsoft.WindowsAzure.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.StreamAnalytics","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","Microsoft.WindowsAzure.Management","2","2000","Assembly Microsoft.WindowsAzure.Management is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Tags","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.TrafficManager","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.UsageAggregates","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.UsageAggregates","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.UsageAggregates","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Websites","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Websites","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Websites","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Websites","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ResourceManager\AzureResourceManager\AzureRM.Websites","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Automation","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Automation","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Automation","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Automation","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Automation","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Azure.Storage","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Azure.Storage","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Azure.Storage","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Azure.Storage","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Azure.Storage","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","AutoMapper.Net4","2","2000","Assembly AutoMapper.Net4 is not referenced from any cmdlets assembly","Remove assembly AutoMapper.Net4 from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","Microsoft.WindowsAzure.Configuration","2","2000","Assembly Microsoft.WindowsAzure.Configuration is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Configuration from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Compute","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ExpressRoute","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ExpressRoute","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ExpressRoute","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ExpressRoute","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ExpressRoute","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\HDInsight","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Networking","AutoMapper.Net4","2","2000","Assembly AutoMapper.Net4 is not referenced from any cmdlets assembly","Remove assembly AutoMapper.Net4 from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Networking","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Networking","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Networking","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","Microsoft.WindowsAzure.Management.Storage","2","2000","Assembly Microsoft.WindowsAzure.Management.Storage is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management.Storage from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RecoveryServices","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RemoteApp","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RemoteApp","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RemoteApp","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RemoteApp","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\RemoteApp","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","AutoMapper.Net4","2","2000","Assembly AutoMapper.Net4 is not referenced from any cmdlets assembly","Remove assembly AutoMapper.Net4 from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.WindowsAzure.Configuration","2","2000","Assembly Microsoft.WindowsAzure.Configuration is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Configuration from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.WindowsAzure.Management.TrafficManager","2","2000","Assembly Microsoft.WindowsAzure.Management.TrafficManager is not referenced from any cmdlets assembly","Remove assembly Microsoft.WindowsAzure.Management.TrafficManager from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Services","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Sql","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Sql","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Sql","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Sql","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\Sql","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\StorSimple","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\StorSimple","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\StorSimple","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\StorSimple","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\StorSimple","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.Data.Edm","2","2000","Assembly Microsoft.Data.Edm is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Edm from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.Data.OData","2","2000","Assembly Microsoft.Data.OData is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.OData from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.Data.Services.Client","2","2000","Assembly Microsoft.Data.Services.Client is not referenced from any cmdlets assembly","Remove assembly Microsoft.Data.Services.Client from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms","2","2000","Assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms is not referenced from any cmdlets assembly","Remove assembly Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.Threading.Tasks.Extensions.Desktop","2","2000","Assembly Microsoft.Threading.Tasks.Extensions.Desktop is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions.Desktop from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","Microsoft.Threading.Tasks.Extensions","2","2000","Assembly Microsoft.Threading.Tasks.Extensions is not referenced from any cmdlets assembly","Remove assembly Microsoft.Threading.Tasks.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","System.Net.Http.Extensions","2","2000","Assembly System.Net.Http.Extensions is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Extensions from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","System.Net.Http.Primitives","2","2000","Assembly System.Net.Http.Primitives is not referenced from any cmdlets assembly","Remove assembly System.Net.Http.Primitives from the project and regenerate the Wix file" +"src\Package\Debug\ServiceManagement\Azure\TrafficManager","System.Spatial","2","2000","Assembly System.Spatial is not referenced from any cmdlets assembly","Remove assembly System.Spatial from the project and regenerate the Wix file" diff --git a/tools/StaticAnalysis/Exceptions/HelpIssues.csv b/tools/StaticAnalysis/Exceptions/HelpIssues.csv new file mode 100644 index 000000000000..28c9bc941b80 --- /dev/null +++ b/tools/StaticAnalysis/Exceptions/HelpIssues.csv @@ -0,0 +1,112 @@ +"Assembly","HelpFile","Target","Severity","ProblemId","Description","Remediation" +"Microsoft.Azure.Commands.ResourceManager.Automation.dll","Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.GetAzureAutomationJobOutputRecord","1","6050","Help missing for cmdlet Get-AzureRmAutomationJobOutputRecord implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.GetAzureAutomationJobOutputRecord","Add Help record for cmdlet Get-AzureRmAutomationJobOutputRecord to help file." +"Microsoft.Azure.Commands.ResourceManager.Automation.dll","Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationDscNodeConfiguration","1","6050","Help missing for cmdlet Remove-AzureRmAutomationDscNodeConfiguration implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationDscNodeConfiguration","Add Help record for cmdlet Remove-AzureRmAutomationDscNodeConfiguration to help file." +"Microsoft.Azure.Commands.ResourceManager.Automation.dll","Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationDscConfiguration","1","6050","Help missing for cmdlet Remove-AzureRmAutomationDscConfiguration implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationDscConfiguration","Add Help record for cmdlet Remove-AzureRmAutomationDscConfiguration to help file." +"Microsoft.AzureStack.Commands.StorageAdmin.dll","Microsoft.AzureStack.Commands.StorageAdmin.dll-Help.xml","Microsoft.AzureStack.Commands.StorageAdmin.GetEvent","1","6050","Help missing for cmdlet Get-ACSEvent implemented by class Microsoft.AzureStack.Commands.StorageAdmin.GetEvent","Add Help record for cmdlet Get-ACSEvent to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.GetAzureRmVMAEMExtension","1","6050","Help missing for cmdlet Get-AzureRmVMAEMExtension implemented by class Microsoft.Azure.Commands.Compute.GetAzureRmVMAEMExtension","Add Help record for cmdlet Get-AzureRmVMAEMExtension to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.RemoveAzureRmVMAEMExtension","1","6050","Help missing for cmdlet Remove-AzureRmVMAEMExtension implemented by class Microsoft.Azure.Commands.Compute.RemoveAzureRmVMAEMExtension","Add Help record for cmdlet Remove-AzureRmVMAEMExtension to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.SetAzureRmVMAEMExtension","1","6050","Help missing for cmdlet Set-AzureRmVMAEMExtension implemented by class Microsoft.Azure.Commands.Compute.SetAzureRmVMAEMExtension","Add Help record for cmdlet Set-AzureRmVMAEMExtension to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.TestAzureRmVMAEMExtension","1","6050","Help missing for cmdlet Test-AzureRmVMAEMExtension implemented by class Microsoft.Azure.Commands.Compute.TestAzureRmVMAEMExtension","Add Help record for cmdlet Test-AzureRmVMAEMExtension to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.SetAzureVMBGInfoExtensionCommand","1","6050","Help missing for cmdlet Set-AzureRmVMBginfoExtension implemented by class Microsoft.Azure.Commands.Compute.SetAzureVMBGInfoExtensionCommand","Add Help record for cmdlet Set-AzureRmVMBginfoExtension to help file." +"Microsoft.Azure.Commands.Compute.dll","Microsoft.Azure.Commands.Compute.dll-Help.xml","Microsoft.Azure.Commands.Compute.SetAzureVMPlanCommand","1","6050","Help missing for cmdlet Set-AzureRmVMPlan implemented by class Microsoft.Azure.Commands.Compute.SetAzureVMPlanCommand","Add Help record for cmdlet Set-AzureRmVMPlan to help file." +"Microsoft.Azure.Commands.Management.Storage.dll","Microsoft.Azure.Commands.Management.Storage.dll-Help.xml","Microsoft.Azure.Commands.Management.Storage.SetAzureRmCurrentStorageAccount","1","6050","Help missing for cmdlet Set-AzureRmCurrentStorageAccount implemented by class Microsoft.Azure.Commands.Management.Storage.SetAzureRmCurrentStorageAccount","Add Help record for cmdlet Set-AzureRmCurrentStorageAccount to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayPathRuleConfigCommand","1","6050","Help missing for cmdlet New-AzureRmApplicationGatewayPathRuleConfig implemented by class Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayPathRuleConfigCommand","Add Help record for cmdlet New-AzureRmApplicationGatewayPathRuleConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.AddAzureApplicationGatewayProbeConfigCommand","1","6050","Help missing for cmdlet Add-AzureRmApplicationGatewayProbeConfig implemented by class Microsoft.Azure.Commands.Network.AddAzureApplicationGatewayProbeConfigCommand","Add Help record for cmdlet Add-AzureRmApplicationGatewayProbeConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureApplicationGatewayProbeConfigCommand","1","6050","Help missing for cmdlet Get-AzureRmApplicationGatewayProbeConfig implemented by class Microsoft.Azure.Commands.Network.GetAzureApplicationGatewayProbeConfigCommand","Add Help record for cmdlet Get-AzureRmApplicationGatewayProbeConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayProbeConfigCommand","1","6050","Help missing for cmdlet New-AzureRmApplicationGatewayProbeConfig implemented by class Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayProbeConfigCommand","Add Help record for cmdlet New-AzureRmApplicationGatewayProbeConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureApplicationGatewayProbeConfigCommand","1","6050","Help missing for cmdlet Remove-AzureRmApplicationGatewayProbeConfig implemented by class Microsoft.Azure.Commands.Network.RemoveAzureApplicationGatewayProbeConfigCommand","Add Help record for cmdlet Remove-AzureRmApplicationGatewayProbeConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.SetAzureApplicationGatewayProbeConfigCommand","1","6050","Help missing for cmdlet Set-AzureRmApplicationGatewayProbeConfig implemented by class Microsoft.Azure.Commands.Network.SetAzureApplicationGatewayProbeConfigCommand","Add Help record for cmdlet Set-AzureRmApplicationGatewayProbeConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.AddAzureApplicationGatewayUrlPathMapConfigCommand","1","6050","Help missing for cmdlet Add-AzureRmApplicationGatewayUrlPathMapConfig implemented by class Microsoft.Azure.Commands.Network.AddAzureApplicationGatewayUrlPathMapConfigCommand","Add Help record for cmdlet Add-AzureRmApplicationGatewayUrlPathMapConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureApplicationGatewayUrlPathMapConfigCommand","1","6050","Help missing for cmdlet Get-AzureRmApplicationGatewayUrlPathMapConfig implemented by class Microsoft.Azure.Commands.Network.GetAzureApplicationGatewayUrlPathMapConfigCommand","Add Help record for cmdlet Get-AzureRmApplicationGatewayUrlPathMapConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayUrlPathMapConfigCommand","1","6050","Help missing for cmdlet New-AzureRmApplicationGatewayUrlPathMapConfig implemented by class Microsoft.Azure.Commands.Network.NewAzureApplicationGatewayUrlPathMapConfigCommand","Add Help record for cmdlet New-AzureRmApplicationGatewayUrlPathMapConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureApplicationGatewayUrlPathMapConfigCommand","1","6050","Help missing for cmdlet Remove-AzureRmApplicationGatewayUrlPathMapConfig implemented by class Microsoft.Azure.Commands.Network.RemoveAzureApplicationGatewayUrlPathMapConfigCommand","Add Help record for cmdlet Remove-AzureRmApplicationGatewayUrlPathMapConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.SetAzureApplicationGatewayUrlPathMapConfigCommand","1","6050","Help missing for cmdlet Set-AzureRmApplicationGatewayUrlPathMapConfig implemented by class Microsoft.Azure.Commands.Network.SetAzureApplicationGatewayUrlPathMapConfigCommand","Add Help record for cmdlet Set-AzureRmApplicationGatewayUrlPathMapConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.AddAzureExpressRouteCircuitAuthorizationCommand","1","6050","Help missing for cmdlet Add-AzureRmExpressRouteCircuitAuthorization implemented by class Microsoft.Azure.Commands.Network.AddAzureExpressRouteCircuitAuthorizationCommand","Add Help record for cmdlet Add-AzureRmExpressRouteCircuitAuthorization to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureExpressRouteCircuitAuthorizationCommand","1","6050","Help missing for cmdlet Get-AzureRmExpressRouteCircuitAuthorization implemented by class Microsoft.Azure.Commands.Network.GetAzureExpressRouteCircuitAuthorizationCommand","Add Help record for cmdlet Get-AzureRmExpressRouteCircuitAuthorization to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureExpressRouteCircuitAuthorizationCommand","1","6050","Help missing for cmdlet New-AzureRmExpressRouteCircuitAuthorization implemented by class Microsoft.Azure.Commands.Network.NewAzureExpressRouteCircuitAuthorizationCommand","Add Help record for cmdlet New-AzureRmExpressRouteCircuitAuthorization to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureExpressRouteCircuitAuthorizationCommand","1","6050","Help missing for cmdlet Remove-AzureRmExpressRouteCircuitAuthorization implemented by class Microsoft.Azure.Commands.Network.RemoveAzureExpressRouteCircuitAuthorizationCommand","Add Help record for cmdlet Remove-AzureRmExpressRouteCircuitAuthorization to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureVpnClientRootCertificates","1","6050","Help missing for cmdlet Get-AzureRmVpnClientRootCertificate implemented by class Microsoft.Azure.Commands.Network.GetAzureVpnClientRootCertificates","Add Help record for cmdlet Get-AzureRmVpnClientRootCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureVpnClientRevokedCertificates","1","6050","Help missing for cmdlet Get-AzureRmVpnClientRevokedCertificate implemented by class Microsoft.Azure.Commands.Network.GetAzureVpnClientRevokedCertificates","Add Help record for cmdlet Get-AzureRmVpnClientRevokedCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.AddAzureVpnClientRootCertificateCommand","1","6050","Help missing for cmdlet Add-AzureRmVpnClientRootCertificate implemented by class Microsoft.Azure.Commands.Network.AddAzureVpnClientRootCertificateCommand","Add Help record for cmdlet Add-AzureRmVpnClientRootCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.AddAzureVpnClientRevokedCertificateCommand","1","6050","Help missing for cmdlet Add-AzureRmVpnClientRevokedCertificate implemented by class Microsoft.Azure.Commands.Network.AddAzureVpnClientRevokedCertificateCommand","Add Help record for cmdlet Add-AzureRmVpnClientRevokedCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureVpnClientRootCertificateCommand","1","6050","Help missing for cmdlet New-AzureRmVpnClientRootCertificate implemented by class Microsoft.Azure.Commands.Network.NewAzureVpnClientRootCertificateCommand","Add Help record for cmdlet New-AzureRmVpnClientRootCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.NewAzureVpnClientRevokedCertificateCommand","1","6050","Help missing for cmdlet New-AzureRmVpnClientRevokedCertificate implemented by class Microsoft.Azure.Commands.Network.NewAzureVpnClientRevokedCertificateCommand","Add Help record for cmdlet New-AzureRmVpnClientRevokedCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.ResizeAzureVirtualNetworkGatewayCommand","1","6050","Help missing for cmdlet Resize-AzureRmVirtualNetworkGateway implemented by class Microsoft.Azure.Commands.Network.ResizeAzureVirtualNetworkGatewayCommand","Add Help record for cmdlet Resize-AzureRmVirtualNetworkGateway to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureVpnClientRevokedCertificateCommand","1","6050","Help missing for cmdlet Remove-AzureRmVpnClientRevokedCertificate implemented by class Microsoft.Azure.Commands.Network.RemoveAzureVpnClientRevokedCertificateCommand","Add Help record for cmdlet Remove-AzureRmVpnClientRevokedCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureVpnClientRootCertificateCommand","1","6050","Help missing for cmdlet Remove-AzureRmVpnClientRootCertificate implemented by class Microsoft.Azure.Commands.Network.RemoveAzureVpnClientRootCertificateCommand","Add Help record for cmdlet Remove-AzureRmVpnClientRootCertificate to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.SetAzureVirtualNetworkGatewayVpnClientConfigCommand","1","6050","Help missing for cmdlet Set-AzureRmVirtualNetworkGatewayVpnClientConfig implemented by class Microsoft.Azure.Commands.Network.SetAzureVirtualNetworkGatewayVpnClientConfigCommand","Add Help record for cmdlet Set-AzureRmVirtualNetworkGatewayVpnClientConfig to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.GetAzureVpnClientPackage","1","6050","Help missing for cmdlet Get-AzureRmVpnClientPackage implemented by class Microsoft.Azure.Commands.Network.GetAzureVpnClientPackage","Add Help record for cmdlet Get-AzureRmVpnClientPackage to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.SetAzureVirtualNetworkGatewayDefaultSiteCommand","1","6050","Help missing for cmdlet Set-AzureRmVirtualNetworkGatewayDefaultSite implemented by class Microsoft.Azure.Commands.Network.SetAzureVirtualNetworkGatewayDefaultSiteCommand","Add Help record for cmdlet Set-AzureRmVirtualNetworkGatewayDefaultSite to help file." +"Microsoft.Azure.Commands.Network.dll","Microsoft.Azure.Commands.Network.dll-Help.xml","Microsoft.Azure.Commands.Network.RemoveAzureVirtualNetworkGatewayDefaultSiteCommand","1","6050","Help missing for cmdlet Remove-AzureRmVirtualNetworkGatewayDefaultSite implemented by class Microsoft.Azure.Commands.Network.RemoveAzureVirtualNetworkGatewayDefaultSiteCommand","Add Help record for cmdlet Remove-AzureRmVirtualNetworkGatewayDefaultSite to help file." +"Microsoft.Azure.Commands.Resources.dll","Microsoft.Azure.Commands.Resources.dll-Help.xml","Microsoft.Azure.Commands.ActiveDirectory.GetAzureADApplicationCommand","1","6050","Help missing for cmdlet Get-AzureRmADApplication implemented by class Microsoft.Azure.Commands.ActiveDirectory.GetAzureADApplicationCommand","Add Help record for cmdlet Get-AzureRmADApplication to help file." +"Microsoft.Azure.Commands.DataLakeStore.dll","Microsoft.Azure.Commands.DataLakeStore.dll-help.xml","Microsoft.Azure.Commands.DataLakeStore.AddAzureDataLakeStoreItemContent","1","6050","Help missing for cmdlet Add-AzureRmDataLakeStoreItemContent implemented by class Microsoft.Azure.Commands.DataLakeStore.AddAzureDataLakeStoreItemContent","Add Help record for cmdlet Add-AzureRmDataLakeStoreItemContent to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSavedSearchCommand","1","6050","Help missing for cmdlet Get-AzureRmOperationalInsightsSavedSearch implemented by class Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSavedSearchCommand","Add Help record for cmdlet Get-AzureRmOperationalInsightsSavedSearch to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSavedSearchResultsCommand","1","6050","Help missing for cmdlet Get-AzureRmOperationalInsightsSavedSearchResults implemented by class Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSavedSearchResultsCommand","Add Help record for cmdlet Get-AzureRmOperationalInsightsSavedSearchResults to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSchemaCommand","1","6050","Help missing for cmdlet Get-AzureRmOperationalInsightsSchema implemented by class Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSchemaCommand","Add Help record for cmdlet Get-AzureRmOperationalInsightsSchema to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSearchResultsCommand","1","6050","Help missing for cmdlet Get-AzureRmOperationalInsightsSearchResults implemented by class Microsoft.Azure.Commands.OperationalInsights.GetAzureOperationalInsightsSearchResultsCommand","Add Help record for cmdlet Get-AzureRmOperationalInsightsSearchResults to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.NewAzureOperationalInsightsSavedSearchCommand","1","6050","Help missing for cmdlet New-AzureRmOperationalInsightsSavedSearch implemented by class Microsoft.Azure.Commands.OperationalInsights.NewAzureOperationalInsightsSavedSearchCommand","Add Help record for cmdlet New-AzureRmOperationalInsightsSavedSearch to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.SetAzureOperationalInsightsSavedSearchCommand","1","6050","Help missing for cmdlet Set-AzureRmOperationalInsightsSavedSearch implemented by class Microsoft.Azure.Commands.OperationalInsights.SetAzureOperationalInsightsSavedSearchCommand","Add Help record for cmdlet Set-AzureRmOperationalInsightsSavedSearch to help file." +"Microsoft.Azure.Commands.OperationalInsights.dll","Microsoft.Azure.Commands.OperationalInsights.dll-Help.xml","Microsoft.Azure.Commands.OperationalInsights.RemoveAzureOperationalInsightsSavedSearchCommand","1","6050","Help missing for cmdlet Remove-AzureRmOperationalInsightsSavedSearch implemented by class Microsoft.Azure.Commands.OperationalInsights.RemoveAzureOperationalInsightsSavedSearchCommand","Add Help record for cmdlet Remove-AzureRmOperationalInsightsSavedSearch to help file." +"Microsoft.Azure.Commands.Sql.dll","Microsoft.Azure.Commands.Sql.dll-Help.xml","Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.GetAzureSqlServerDisasterRecoveryConfiguration","1","6050","Help missing for cmdlet Get-AzureRmSqlServerDisasterRecoveryConfiguration implemented by class Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.GetAzureSqlServerDisasterRecoveryConfiguration","Add Help record for cmdlet Get-AzureRmSqlServerDisasterRecoveryConfiguration to help file." +"Microsoft.Azure.Commands.Sql.dll","Microsoft.Azure.Commands.Sql.dll-Help.xml","Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.GetAzureSqlServerDisasterRecoveryConfigurationActivity","1","6050","Help missing for cmdlet Get-AzureRmSqlServerDisasterRecoveryConfigurationActivity implemented by class Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.GetAzureSqlServerDisasterRecoveryConfigurationActivity","Add Help record for cmdlet Get-AzureRmSqlServerDisasterRecoveryConfigurationActivity to help file." +"Microsoft.Azure.Commands.Sql.dll","Microsoft.Azure.Commands.Sql.dll-Help.xml","Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.NewAzureSqlServerDisasterRecoveryConfiguration","1","6050","Help missing for cmdlet New-AzureRmSqlServerDisasterRecoveryConfiguration implemented by class Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.NewAzureSqlServerDisasterRecoveryConfiguration","Add Help record for cmdlet New-AzureRmSqlServerDisasterRecoveryConfiguration to help file." +"Microsoft.Azure.Commands.Sql.dll","Microsoft.Azure.Commands.Sql.dll-Help.xml","Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.RemoveAzureSqlServerDisasterRecoveryConfiguration","1","6050","Help missing for cmdlet Remove-AzureRmSqlServerDisasterRecoveryConfiguration implemented by class Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.RemoveAzureSqlServerDisasterRecoveryConfiguration","Add Help record for cmdlet Remove-AzureRmSqlServerDisasterRecoveryConfiguration to help file." +"Microsoft.Azure.Commands.Sql.dll","Microsoft.Azure.Commands.Sql.dll-Help.xml","Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.SetAzureSqlServerDisasterRecoveryConfiguration","1","6050","Help missing for cmdlet Set-AzureRmSqlServerDisasterRecoveryConfiguration implemented by class Microsoft.Azure.Commands.Sql.ServerDisasterRecoveryConfiguration.Cmdlet.SetAzureSqlServerDisasterRecoveryConfiguration","Add Help record for cmdlet Set-AzureRmSqlServerDisasterRecoveryConfiguration to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.DisableAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet Disable-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.DisableAzureTrafficManagerEndpoint","Add Help record for cmdlet Disable-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.EnableAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet Enable-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.EnableAzureTrafficManagerEndpoint","Add Help record for cmdlet Enable-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.SetAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet Set-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.SetAzureTrafficManagerEndpoint","Add Help record for cmdlet Set-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.GetAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet Get-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.GetAzureTrafficManagerEndpoint","Add Help record for cmdlet Get-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.RemoveAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet Remove-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.RemoveAzureTrafficManagerEndpoint","Add Help record for cmdlet Remove-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.NewAzureTrafficManagerEndpoint","1","6050","Help missing for cmdlet New-AzureRmTrafficManagerEndpoint implemented by class Microsoft.Azure.Commands.TrafficManager.NewAzureTrafficManagerEndpoint","Add Help record for cmdlet New-AzureRmTrafficManagerEndpoint to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.DisableAzureTrafficManagerProfile","1","6050","Help missing for cmdlet Disable-AzureRmTrafficManagerProfile implemented by class Microsoft.Azure.Commands.TrafficManager.DisableAzureTrafficManagerProfile","Add Help record for cmdlet Disable-AzureRmTrafficManagerProfile to help file." +"Microsoft.Azure.Commands.TrafficManager.dll","Microsoft.Azure.Commands.TrafficManager.dll-help.xml","Microsoft.Azure.Commands.TrafficManager.EnableAzureTrafficManagerProfile","1","6050","Help missing for cmdlet Enable-AzureRmTrafficManagerProfile implemented by class Microsoft.Azure.Commands.TrafficManager.EnableAzureTrafficManagerProfile","Add Help record for cmdlet Enable-AzureRmTrafficManagerProfile to help file." +"Microsoft.Azure.Commands.Automation.dll","Microsoft.Azure.Commands.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationConnection","1","6050","Help missing for cmdlet Remove-AzureAutomationConnection implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationConnection","Add Help record for cmdlet Remove-AzureAutomationConnection to help file." +"Microsoft.Azure.Commands.Automation.dll","Microsoft.Azure.Commands.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationConnectionType","1","6050","Help missing for cmdlet Remove-AzureAutomationConnectionType implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.RemoveAzureAutomationConnectionType","Add Help record for cmdlet Remove-AzureAutomationConnectionType to help file." +"Microsoft.Azure.Commands.Automation.dll","Microsoft.Azure.Commands.Automation.dll-help.xml","Microsoft.Azure.Commands.Automation.Cmdlet.SetAzureAutomationConnectionFieldValue","1","6050","Help missing for cmdlet Set-AzureAutomationConnectionFieldValue implemented by class Microsoft.Azure.Commands.Automation.Cmdlet.SetAzureAutomationConnectionFieldValue","Add Help record for cmdlet Set-AzureAutomationConnectionFieldValue to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.Extensions.NewAzureVMSqlServerKeyVaultCredentialConfigCommand","1","6050","Help missing for cmdlet New-AzureVMSqlServerKeyVaultCredentialConfig implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.Extensions.NewAzureVMSqlServerKeyVaultCredentialConfigCommand","Add Help record for cmdlet New-AzureVMSqlServerKeyVaultCredentialConfig to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.SetAzureBootDiagnosticsCommand","1","6050","Help missing for cmdlet Set-AzureBootDiagnostics implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.SetAzureBootDiagnosticsCommand","Add Help record for cmdlet Set-AzureBootDiagnostics to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Extensions.GetAzureServiceAvailableExtensionCommand","1","6050","Help missing for cmdlet Get-AzurePlatformExtension implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Extensions.GetAzureServiceAvailableExtensionCommand","Add Help record for cmdlet Get-AzurePlatformExtension to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.ImagePublishing.NewAzurePlatformMarketplaceImageConfig","1","6050","Help missing for cmdlet New-AzurePlatformMarketplaceImageConfig implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.ImagePublishing.NewAzurePlatformMarketplaceImageConfig","Add Help record for cmdlet New-AzurePlatformMarketplaceImageConfig to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.ImagePublishing.NewAzurePlatformComputeImageConfig","1","6050","Help missing for cmdlet New-AzurePlatformComputeImageConfig implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.ImagePublishing.NewAzurePlatformComputeImageConfig","Add Help record for cmdlet New-AzurePlatformComputeImageConfig to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureCrossConnectionCommand","1","6050","Help missing for cmdlet Get-AzureCrossConnection implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureCrossConnectionCommand","Add Help record for cmdlet Get-AzureCrossConnection to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.NewAzureCrossConnectionCommand","1","6050","Help missing for cmdlet New-AzureCrossConnection implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.NewAzureCrossConnectionCommand","Add Help record for cmdlet New-AzureCrossConnection to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.SetAzureCrossConnectionCommand","1","6050","Help missing for cmdlet Set-AzureCrossConnection implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.SetAzureCrossConnectionCommand","Add Help record for cmdlet Set-AzureCrossConnection to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringArpInfoCommand","1","6050","Help missing for cmdlet Get-AzureDedicatedCircuitPeeringArpInfo implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringArpInfoCommand","Add Help record for cmdlet Get-AzureDedicatedCircuitPeeringArpInfo to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringRouteTableInfoCommand","1","6050","Help missing for cmdlet Get-AzureDedicatedCircuitPeeringRouteTableInfo implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringRouteTableInfoCommand","Add Help record for cmdlet Get-AzureDedicatedCircuitPeeringRouteTableInfo to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringRouteTableSummaryCommand","1","6050","Help missing for cmdlet Get-AzureDedicatedCircuitPeeringRouteTableSummary implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringRouteTableSummaryCommand","Add Help record for cmdlet Get-AzureDedicatedCircuitPeeringRouteTableSummary to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringStatsCommand","1","6050","Help missing for cmdlet Get-AzureDedicatedCircuitStats implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.GetAzureDedicatedCircuitPeeringStatsCommand","Add Help record for cmdlet Get-AzureDedicatedCircuitStats to help file." +"Microsoft.WindowsAzure.Commands.ExpressRoute.dll","Microsoft.WindowsAzure.Commands.ExpressRoute.dll-Help.xml","Microsoft.WindowsAzure.Commands.ExpressRoute.SetAzureDedicatedCircuitPropertiesCommand","1","6050","Help missing for cmdlet Set-AzureDedicatedCircuitProperties implemented by class Microsoft.WindowsAzure.Commands.ExpressRoute.SetAzureDedicatedCircuitPropertiesCommand","Add Help record for cmdlet Set-AzureDedicatedCircuitProperties to help file." +"Microsoft.WindowsAzure.Commands.HDInsight.dll","Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.xml","Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.AddAzureHDInsightScriptActionCmdlet","1","6050","Help missing for cmdlet Add-AzureHDInsightScriptAction implemented by class Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.AddAzureHDInsightScriptActionCmdlet","Add Help record for cmdlet Add-AzureHDInsightScriptAction to help file." +"Microsoft.WindowsAzure.Commands.HDInsight.dll","Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.xml","Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.GrantAzureHdinsightRdpAccessCmdlet","1","6050","Help missing for cmdlet Grant-AzureHDInsightRdpAccess implemented by class Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.GrantAzureHdinsightRdpAccessCmdlet","Add Help record for cmdlet Grant-AzureHDInsightRdpAccess to help file." +"Microsoft.WindowsAzure.Commands.HDInsight.dll","Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.xml","Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.RevokeAzureHDInsightRdpAccessCmdlet","1","6050","Help missing for cmdlet Revoke-AzureHDInsightRdpAccess implemented by class Microsoft.WindowsAzure.Management.HDInsight.Cmdlet.PSCmdlets.RevokeAzureHDInsightRdpAccessCmdlet","Add Help record for cmdlet Revoke-AzureHDInsightRdpAccess to help file." +"Microsoft.WindowsAzure.Commands.HDInsight.dll","Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.xml","Microsoft.WindowsAzure.Commands.HDInsight.Cmdlet.PSCmdlets.SetAzureHDInsightClusterSizeCmdlet","1","6050","Help missing for cmdlet Set-AzureHDInsightClusterSize implemented by class Microsoft.WindowsAzure.Commands.HDInsight.Cmdlet.PSCmdlets.SetAzureHDInsightClusterSizeCmdlet","Add Help record for cmdlet Set-AzureHDInsightClusterSize to help file." +"Microsoft.Azure.Commands.ManagedCache.dll","Microsoft.Azure.Commands.ManagedCache.dll-help.xml","Microsoft.Azure.Commands.ManagedCache.AzureManagedCacheLocation","1","6050","Help missing for cmdlet Get-AzureManagedCacheLocation implemented by class Microsoft.Azure.Commands.ManagedCache.AzureManagedCacheLocation","Add Help record for cmdlet Get-AzureManagedCacheLocation to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkConnectionGateway","1","6050","Help missing for cmdlet Get-AzureVirtualNetworkGatewayConnection implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkConnectionGateway","Add Help record for cmdlet Get-AzureVirtualNetworkGatewayConnection to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayDiagnostics","1","6050","Help missing for cmdlet Get-AzureVirtualNetworkGatewayDiagnostics implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayDiagnostics","Add Help record for cmdlet Get-AzureVirtualNetworkGatewayDiagnostics to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayIPsecParameters","1","6050","Help missing for cmdlet Get-AzureVirtualNetworkGatewayIPsecParameters implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayIPsecParameters","Add Help record for cmdlet Get-AzureVirtualNetworkGatewayIPsecParameters to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayKey","1","6050","Help missing for cmdlet Get-AzureVirtualNetworkGatewayKey implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGatewayKey","Add Help record for cmdlet Get-AzureVirtualNetworkGatewayKey to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureVirtualNetworkGatewayCommand","1","6050","Help missing for cmdlet New-AzureVirtualNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureVirtualNetworkGatewayCommand","Add Help record for cmdlet New-AzureVirtualNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureVirtualNetworkGatewayConnectionCommand","1","6050","Help missing for cmdlet New-AzureVirtualNetworkGatewayConnection implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureVirtualNetworkGatewayConnectionCommand","Add Help record for cmdlet New-AzureVirtualNetworkGatewayConnection to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGatewayKey","1","6050","Help missing for cmdlet Reset-AzureVirtualNetworkGatewayKey implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGatewayKey","Add Help record for cmdlet Reset-AzureVirtualNetworkGatewayKey to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.SetAzureVirtualNetworkGatewayIPsecParameters","1","6050","Help missing for cmdlet Set-AzureVirtualNetworkGatewayIPsecParameters implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.SetAzureVirtualNetworkGatewayIPsecParameters","Add Help record for cmdlet Set-AzureVirtualNetworkGatewayIPsecParameters to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.SetAzureVirtualNetworkGatewayKey","1","6050","Help missing for cmdlet Set-AzureVirtualNetworkGatewayKey implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.SetAzureVirtualNetworkGatewayKey","Add Help record for cmdlet Set-AzureVirtualNetworkGatewayKey to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.StartAzureVirtualNetworkGatewayDiagnostics","1","6050","Help missing for cmdlet Start-AzureVirtualNetworkGatewayDiagnostics implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.StartAzureVirtualNetworkGatewayDiagnostics","Add Help record for cmdlet Start-AzureVirtualNetworkGatewayDiagnostics to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.StopAzureVirtualNetworkGatewayDiagnostics","1","6050","Help missing for cmdlet Stop-AzureVirtualNetworkGatewayDiagnostics implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.StopAzureVirtualNetworkGatewayDiagnostics","Add Help record for cmdlet Stop-AzureVirtualNetworkGatewayDiagnostics to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureLocalNetworkGateway","1","6050","Help missing for cmdlet Get-AzureLocalNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureLocalNetworkGateway","Add Help record for cmdlet Get-AzureLocalNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGateway","1","6050","Help missing for cmdlet Get-AzureVirtualNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.GetAzureVirtualNetworkGateway","Add Help record for cmdlet Get-AzureVirtualNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureLocalNetworkGateway","1","6050","Help missing for cmdlet New-AzureLocalNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.NewAzureLocalNetworkGateway","Add Help record for cmdlet New-AzureLocalNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureLocalNetworkGateway","1","6050","Help missing for cmdlet Remove-AzureLocalNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureLocalNetworkGateway","Add Help record for cmdlet Remove-AzureLocalNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureVirtualNetworkGateway","1","6050","Help missing for cmdlet Remove-AzureVirtualNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureVirtualNetworkGateway","Add Help record for cmdlet Remove-AzureVirtualNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureVirtualNetworkGatewayConnection","1","6050","Help missing for cmdlet Remove-AzureVirtualNetworkGatewayConnection implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.RemoveAzureVirtualNetworkGatewayConnection","Add Help record for cmdlet Remove-AzureVirtualNetworkGatewayConnection to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGateway","1","6050","Help missing for cmdlet Reset-AzureVirtualNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGateway","Add Help record for cmdlet Reset-AzureVirtualNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResizeAzureVirtualNetworkGateway","1","6050","Help missing for cmdlet Resize-AzureVirtualNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResizeAzureVirtualNetworkGateway","Add Help record for cmdlet Resize-AzureVirtualNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureLocalNetworkGateway","1","6050","Help missing for cmdlet Reset-AzureLocalNetworkGateway implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureLocalNetworkGateway","Add Help record for cmdlet Reset-AzureLocalNetworkGateway to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGatewayConnection","1","6050","Help missing for cmdlet Reset-AzureVirtualNetworkGatewayConnection implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.Network.Gateway.ResetAzureVirtualNetworkGatewayConnection","Add Help record for cmdlet Reset-AzureVirtualNetworkGatewayConnection to help file." +"Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll","Microsoft.WindowsAzure.Commands.ServiceManagement.Network.dll-help.xml","Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.GetAzureNetworkSecurityGroupConfigCommand","1","6050","Help missing for cmdlet Get-AzureNetworkSecurityGroupConfig implemented by class Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.GetAzureNetworkSecurityGroupConfigCommand","Add Help record for cmdlet Get-AzureNetworkSecurityGroupConfig to help file." +"Microsoft.WindowsAzure.Commands.RemoteApp.dll","Microsoft.WindowsAzure.Commands.RemoteApp.dll-help.xml","Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.ClearAzureRemoteAppVmStaleAdObject","1","6050","Help missing for cmdlet Clear-AzureRemoteAppVmStaleAdObject implemented by class Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.ClearAzureRemoteAppVmStaleAdObject","Add Help record for cmdlet Clear-AzureRemoteAppVmStaleAdObject to help file." +"Microsoft.WindowsAzure.Commands.RemoteApp.dll","Microsoft.WindowsAzure.Commands.RemoteApp.dll-help.xml","Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.GetAzureRemoteAppVm","1","6050","Help missing for cmdlet Get-AzureRemoteAppVM implemented by class Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.GetAzureRemoteAppVm","Add Help record for cmdlet Get-AzureRemoteAppVM to help file." +"Microsoft.WindowsAzure.Commands.RemoteApp.dll","Microsoft.WindowsAzure.Commands.RemoteApp.dll-help.xml","Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.GetAzureRemoteAppVmStaleAdObject","1","6050","Help missing for cmdlet Get-AzureRemoteAppVmStaleAdObject implemented by class Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.GetAzureRemoteAppVmStaleAdObject","Add Help record for cmdlet Get-AzureRemoteAppVmStaleAdObject to help file." +"Microsoft.WindowsAzure.Commands.RemoteApp.dll","Microsoft.WindowsAzure.Commands.RemoteApp.dll-help.xml","Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.RestartAzureRemoteAppVm","1","6050","Help missing for cmdlet Restart-AzureRemoteAppVM implemented by class Microsoft.WindowsAzure.Management.RemoteApp.Cmdlets.RestartAzureRemoteAppVm","Add Help record for cmdlet Restart-AzureRemoteAppVM to help file." +"Microsoft.WindowsAzure.Commands.Profile.dll","Microsoft.WindowsAzure.Commands.Profile.dll-Help.xml","Microsoft.WindowsAzure.Commands.Profile.EnableAzureDataCollectionCommand","1","6050","Help missing for cmdlet Enable-AzureDataCollection implemented by class Microsoft.WindowsAzure.Commands.Profile.EnableAzureDataCollectionCommand","Add Help record for cmdlet Enable-AzureDataCollection to help file." +"Microsoft.WindowsAzure.Commands.Profile.dll","Microsoft.WindowsAzure.Commands.Profile.dll-Help.xml","Microsoft.WindowsAzure.Commands.Profile.DisableAzureDataCollectionCommand","1","6050","Help missing for cmdlet Disable-AzureDataCollection implemented by class Microsoft.WindowsAzure.Commands.Profile.DisableAzureDataCollectionCommand","Add Help record for cmdlet Disable-AzureDataCollection to help file." +"Microsoft.WindowsAzure.Commands.SqlDatabase.dll","Microsoft.WindowsAzure.Commands.SqlDatabase.dll-Help.xml","Microsoft.WindowsAzure.Commands.SqlDatabase.Database.Cmdlet.GetAzureSqlDatabaseUsages","1","6050","Help missing for cmdlet Get-AzureSqlDatabaseUsages implemented by class Microsoft.WindowsAzure.Commands.SqlDatabase.Database.Cmdlet.GetAzureSqlDatabaseUsages","Add Help record for cmdlet Get-AzureSqlDatabaseUsages to help file." diff --git a/tools/StaticAnalysis/Exceptions/MissingAssemblies.csv b/tools/StaticAnalysis/Exceptions/MissingAssemblies.csv new file mode 100644 index 000000000000..0423039893b0 --- /dev/null +++ b/tools/StaticAnalysis/Exceptions/MissingAssemblies.csv @@ -0,0 +1,6 @@ +"Directory","Assembly Name","Assembly Version","Referencing Assembly","Severity","ProblemId","Description","Remediation" +"src\Package\Debug\ServiceManagement\Azure\Compute","Microsoft.Web.Deployment","9.0.0.0","Microsoft.WindowsAzure.Commands.Utilities","0","3000","Missing assembly Microsoft.Web.Deployment referenced from Microsoft.WindowsAzure.Commands.Utilities","Ensure that the assembly is included in the Wix file or directory" +"src\Package\Debug\ServiceManagement\Azure\ManagedCache","Microsoft.Web.Deployment","9.0.0.0","Microsoft.WindowsAzure.Commands.Utilities","0","3000","Missing assembly Microsoft.Web.Deployment referenced from Microsoft.WindowsAzure.Commands.Utilities","Ensure that the assembly is included in the Wix file or directory" +"src\Package\Debug\ServiceManagement\Azure\Networking","Microsoft.Web.Deployment","9.0.0.0","Microsoft.WindowsAzure.Commands.Utilities","0","3000","Missing assembly Microsoft.Web.Deployment referenced from Microsoft.WindowsAzure.Commands.Utilities","Ensure that the assembly is included in the Wix file or directory" +"src\Package\Debug\ServiceManagement\Azure\Services","Microsoft.Web.Deployment","9.0.0.0","Microsoft.WindowsAzure.Commands.Utilities","0","3000","Missing assembly Microsoft.Web.Deployment referenced from Microsoft.WindowsAzure.Commands.Utilities","Ensure that the assembly is included in the Wix file or directory" +"src\Package\Debug\ServiceManagement\Azure\Sql","Microsoft.Web.Deployment","9.0.0.0","Microsoft.WindowsAzure.Commands.Utilities","0","3000","Missing assembly Microsoft.Web.Deployment referenced from Microsoft.WindowsAzure.Commands.Utilities","Ensure that the assembly is included in the Wix file or directory" diff --git a/tools/StaticAnalysis/HelpAnalyzer/CmdletHelpParser.cs b/tools/StaticAnalysis/HelpAnalyzer/CmdletHelpParser.cs index c1d7d1e0476f..0922523add34 100644 --- a/tools/StaticAnalysis/HelpAnalyzer/CmdletHelpParser.cs +++ b/tools/StaticAnalysis/HelpAnalyzer/CmdletHelpParser.cs @@ -27,6 +27,9 @@ public class CmdletHelpParser public const string MamlSchemaUri = "http://schemas.microsoft.com/maml/2004/10"; public const string MamlDevSchemaUri = "http://schemas.microsoft.com/maml/dev/2004/10"; public const string CommandSchemaUri = "http://schemas.microsoft.com/maml/dev/command/2004/10"; + const int MissingCommandName = 5000; + const int MissingCommandDetails = 5010; + const int InvalidHelpFile = 5020; public static IList GetHelpTopics(string helpPath, ReportLogger logger) { IList cmdlets = new List(); @@ -49,6 +52,7 @@ public static IList GetHelpTopics(string helpPath, ReportLogger GetHelpTopics(string helpPath, ReportLogger GetHelpTopics(string helpPath, ReportLogger public class HelpAnalyzer : IStaticAnalyzer { + const int MissingHelp = 6050; public HelpAnalyzer() { Name = "Help Analyzer"; @@ -66,7 +67,7 @@ public void Analyze(IEnumerable scopes) h.HelpFile = helpFileName; h.Assembly = cmdletFileName; }, "Cmdlet"); - var proxy = AppDomainHelpers.CreateProxy(directory, out _appDomain); + var proxy = EnvironmentHelpers.CreateProxy(directory, out _appDomain); var cmdlets = proxy.GetCmdlets(cmdletFile); var helpRecords = CmdletHelpParser.GetHelpTopics(helpFile, helpLogger); ValidateHelpRecords(cmdlets, helpRecords, helpLogger); @@ -92,6 +93,7 @@ private void ValidateHelpRecords(IList cmdlets, IList public string Target { get; set; } + + public int ProblemId { get; set; } public string Description { get; set; } public string Remediation { get; set; } public int Severity { get; set; } public string PrintHeaders() { - return "\"Assembly\",\"HelpFile\",\"Target\",\"Severity\",\"Description\",\"Remediation\""; + return "\"Assembly\",\"HelpFile\",\"Target\",\"Severity\",\"ProblemId\",\"Description\",\"Remediation\""; } public string FormatRecord() { - return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\"", - Assembly, HelpFile, Target, Severity, Description, Remediation); + return string.Format("\"{0}\",\"{1}\",\"{2}\",\"{3}\",\"{4}\",\"{5}\",\"{6}\"", + Assembly, HelpFile, Target, Severity, ProblemId, Description, Remediation); + } + + public bool Match(IReportRecord other) + { + var result = false; + var record = other as HelpIssue; + if (record != null) + { + result = string.Equals(record.Assembly, Assembly, StringComparison.OrdinalIgnoreCase) && + string.Equals(record.HelpFile, HelpFile, StringComparison.OrdinalIgnoreCase) && + string.Equals(record.Target, Target, StringComparison.OrdinalIgnoreCase) && + record.ProblemId == ProblemId; + } + + return result; + } + + public IReportRecord Parse(string line) + { + var matcher = "\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\",\"([^\"]+)\""; + var match = Regex.Match(line, matcher); + if (!match.Success || match.Groups.Count < 8) + { + throw new InvalidOperationException(string.Format("Could not parse '{0}' as HelpIssue record", line)); + } + + Assembly = match.Groups[1].Value; + HelpFile = match.Groups[2].Value; + Target = match.Groups[3].Value; + Severity = int.Parse(match.Groups[4].Value); + ProblemId = int.Parse(match.Groups[5].Value); + Description = match.Groups[6].Value; + Remediation = match.Groups[7].Value; + return this; } } } diff --git a/tools/StaticAnalysis/IReportRecord.cs b/tools/StaticAnalysis/IReportRecord.cs index ab0c97f50171..3ad7328b0f11 100644 --- a/tools/StaticAnalysis/IReportRecord.cs +++ b/tools/StaticAnalysis/IReportRecord.cs @@ -12,6 +12,8 @@ // limitations under the License. // ---------------------------------------------------------------------------------- +using System.Security.Cryptography.X509Certificates; + namespace StaticAnalysis { /// @@ -19,10 +21,13 @@ namespace StaticAnalysis /// public interface IReportRecord { + int ProblemId { get; set; } string Description { get; set; } string Remediation { get; set; } int Severity { get; set; } string PrintHeaders(); string FormatRecord(); + bool Match(IReportRecord other); + IReportRecord Parse(string line); } } diff --git a/tools/StaticAnalysis/Program.cs b/tools/StaticAnalysis/Program.cs index 9f989039b0b1..02b1f5caa272 100644 --- a/tools/StaticAnalysis/Program.cs +++ b/tools/StaticAnalysis/Program.cs @@ -55,7 +55,15 @@ public static void Main(string[] args) logReportsDirectoryWarning = false; } - var logger = new ConsoleLogger(reportsDirectory); + var exceptionsDirectory = Path.Combine(reportsDirectory, "Exceptions"); + bool useExceptions = true; + if (args.Length > 2) + { + bool.TryParse(args[2], out useExceptions); + } + + var logger = useExceptions? new ConsoleLogger(reportsDirectory, exceptionsDirectory) : + new ConsoleLogger(reportsDirectory); if (logReportsDirectoryWarning) { @@ -72,6 +80,7 @@ public static void Main(string[] args) } logger.WriteReports(); + logger.CheckForIssues(2); } } } diff --git a/tools/StaticAnalysis/ReportLogger.cs b/tools/StaticAnalysis/ReportLogger.cs index c836be697c1c..767215883bfd 100644 --- a/tools/StaticAnalysis/ReportLogger.cs +++ b/tools/StaticAnalysis/ReportLogger.cs @@ -13,7 +13,9 @@ // ---------------------------------------------------------------------------------- using System.Collections.Generic; +using System.IO; using System.Linq; +using System.Runtime.InteropServices; namespace StaticAnalysis { @@ -24,10 +26,18 @@ public abstract class ReportLogger { private AnalysisLogger _parent; private string _outputFile; + private string _exceptionsFilename; + public ReportLogger(string fileName, AnalysisLogger parent) + : this(fileName, null, parent) + { + } + + public ReportLogger(string fileName, string exceptionsFilename, AnalysisLogger parent) { _parent = parent; _outputFile = fileName; + _exceptionsFilename = exceptionsFilename; } protected AnalysisLogger ParentLogger { get { return _parent; } } @@ -54,15 +64,31 @@ public virtual void WriteWarning(string message) /// A typed report logger /// /// The type of the report this logger will log. - public class ReportLogger : ReportLogger where T : IReportRecord, new() + public class ReportLogger : ReportLogger where T : class, IReportRecord, new() { public ReportLogger(string fileName, AnalysisLogger logger) + : this(fileName, null, logger) + { + Decorator = Decorator.Create(); + } + + public ReportLogger(string fileName, string exceptionsFileName, AnalysisLogger logger) : base(fileName, logger) { Decorator = Decorator.Create(); + if (exceptionsFileName != null && File.Exists(exceptionsFileName)) + { + var records = File.ReadAllLines(exceptionsFileName); + for (int i = 1; i < records.Length; ++i) + { + var record = new T(); + _exceptionRecords.Add(record.Parse(records[i]) as T); + } + } } private IList _records = new List(); + private IList _exceptionRecords = new List(); public Decorator Decorator { get; protected set; } /// @@ -72,7 +98,10 @@ public ReportLogger(string fileName, AnalysisLogger logger) public void LogRecord(T record) { Decorator.Apply(record); - _records.Add(record); + if (!_exceptionRecords.Any(r => r.Match(record))) + { + _records.Add(record); + } } public override IList Records diff --git a/tools/StaticAnalysis/StaticAnalysis.Test/Constants.cs b/tools/StaticAnalysis/StaticAnalysis.Test/Constants.cs new file mode 100644 index 000000000000..57f52de4ab0d --- /dev/null +++ b/tools/StaticAnalysis/StaticAnalysis.Test/Constants.cs @@ -0,0 +1,41 @@ + +// ---------------------------------------------------------------------------------- +// +// Copyright Microsoft Corporation +// Licensed under the Apache License, Version 2.0 (the "License"); +// you may not use this file except in compliance with the License. +// You may obtain a copy of the License at +// http://www.apache.org/licenses/LICENSE-2.0 +// Unless required by applicable law or agreed to in writing, software +// distributed under the License is distributed on an "AS IS" BASIS, +// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +// See the License for the specific language governing permissions and +// limitations under the License. +// ---------------------------------------------------------------------------------- + +namespace StaticAnalysis.Test +{ + public class Category + { + // Service + public const string Service = "Service"; + + public const string All = "All"; + + // Owners + public const string OneSDK = "OneSDK"; + + // Acceptance type + public const string AcceptanceType = "AcceptanceType"; + + public const string CIT = "CIT"; + + public const string BVT = "BVT"; + + public const string CheckIn = "CheckIn"; + + // Run Type + public const string RunType = "RunType"; + public const string LiveOnly = "LiveOnly"; + } +} diff --git a/tools/StaticAnalysis/StaticAnalysis.Test/MatchingTests.cs b/tools/StaticAnalysis/StaticAnalysis.Test/MatchingTests.cs new file mode 100644 index 000000000000..705b4eea38a8 --- /dev/null +++ b/tools/StaticAnalysis/StaticAnalysis.Test/MatchingTests.cs @@ -0,0 +1,374 @@ +// ---------------------------------------------------------------------------------- +// +// Copyright Microsoft Corporation +// Licensed under the Apache License, Version 2.0 (the "License"); +// you may not use this file except in compliance with the License. +// You may obtain a copy of the License at +// http://www.apache.org/licenses/LICENSE-2.0 +// Unless required by applicable law or agreed to in writing, software +// distributed under the License is distributed on an "AS IS" BASIS, +// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +// See the License for the specific language governing permissions and +// limitations under the License. +// ---------------------------------------------------------------------------------- + +using System; +using System.Collections.Generic; +using System.Text; +using StaticAnalysis.DependencyAnalyzer; +using StaticAnalysis.HelpAnalyzer; +using Xunit; + +namespace StaticAnalysis.Test +{ + public class MatchingTests + { + private static Random Random = new Random(); + private static T GetClone(T baseValue) where T : class, ICloneable + { + T result = null; + if (baseValue != null) + { + result = baseValue.Clone() as T; + } + + return result; + } + + private static AssemblyVersionConflict CreateAssemblyVersionConflict(string directory, string assembly, string parentAssembly, + int problemId, bool vary = false) + { + return new AssemblyVersionConflict + { + Directory = directory != null && vary? GetClone(directory).ToUpperInvariant() : GetClone(directory), + AssemblyName = assembly!= null && vary ? GetClone(assembly).ToLowerInvariant() : GetClone(assembly), + ParentAssembly = parentAssembly != null && vary? GetClone(parentAssembly).ToUpperInvariant() : GetClone(parentAssembly), + ProblemId = problemId, + Description = GetRandomString(), + Remediation = GetRandomString(), + ActualVersion = GetRandomVersion(), + ExpectedVersion = GetRandomVersion(), + Severity = Random.Next() + }; + } + + private static HelpIssue CreateHelpIssue(string assembly, string helpFile, string target, int problemId, bool vary = false) + { + return new HelpIssue + { + Assembly = assembly != null && vary? GetClone(assembly).ToUpperInvariant() : GetClone(assembly), + HelpFile = assembly!= null && vary ? GetClone(helpFile).ToLowerInvariant() : GetClone(helpFile), + Target = target != null && vary? GetClone(target).ToUpperInvariant() : GetClone(target), + ProblemId = problemId, + Description = GetRandomString(), + Remediation = GetRandomString(), + Severity = Random.Next() + }; + } + + + private static ExtraAssembly CreateExtraAssembly(string directory, string assembly, + int problemId, bool vary = false) + { + return new ExtraAssembly + { + Directory = directory != null && vary? GetClone(directory).ToUpperInvariant() : GetClone(directory), + AssemblyName = assembly!= null && vary ? GetClone(assembly).ToLowerInvariant() : GetClone(assembly), + ProblemId = problemId, + Description = GetRandomString(), + Remediation = GetRandomString(), + Severity = Random.Next() + }; + } + + private static MissingAssembly CreateMissingAssembly(string directory, string assembly, + string version, string refAssembly, int problemId, bool vary = false) + { + return new MissingAssembly + { + Directory = directory != null && vary? GetClone(directory).ToUpperInvariant() : GetClone(directory), + AssemblyName = assembly!= null && vary ? GetClone(assembly).ToLowerInvariant() : GetClone(assembly), + AssemblyVersion = version, + ReferencingAssembly = refAssembly, + ProblemId = problemId, + Description = GetRandomString(), + Remediation = GetRandomString(), + Severity = Random.Next(), + }; + } + + private static SharedAssemblyConflict CreateSharedAssemblyConflict(string assembly, string version, + int problemId, bool vary = false) + { + return new SharedAssemblyConflict + { + + AssemblyName = assembly!= null && vary ? GetClone(assembly).ToLowerInvariant() : GetClone(assembly), + AssemblyVersion = Version.Parse(version), + ProblemId = problemId, + Description = GetRandomString(), + Remediation = GetRandomString(), + Severity = Random.Next(), + AssemblyPathsAndFileVersions = GetRandomStringVersionList() + }; + } + + private static List> GetRandomStringVersionList() + { + var result = new List>(); + result.Add(new Tuple(GetRandomString(), GetRandomVersion())); + result.Add(new Tuple(GetRandomString(), GetRandomVersion())); + return result; + } + + private static Version GetRandomVersion() + { + return new Version(Random.Next(), Random.Next(), Random.Next(), Random.Next()); + } + + private static string GetRandomString() + { + var length = Random.Next(5, 30); + var builder = new StringBuilder(); + for (int i = 0; i < length; ++i) + { + builder.Append(Random.Next('A', 'z')); + } + + return builder.ToString(); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , null, int.MinValue)] + [InlineData("", "", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", "MyParentAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "My.Longer.ParentAssembly", 2000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanMatchAsssemblyVersionConflict(string directory, string assembly, string parentAssembly, int problemId) + { + var conflict1 = CreateAssemblyVersionConflict(directory, assembly, parentAssembly, problemId); + var conflict2 = CreateAssemblyVersionConflict(directory, assembly, parentAssembly, problemId, true); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("dir1/dir2/file/", "MyAssembly", "MyParentAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "My.Longer.ParentAssembly", 2000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanRoundTripAssemblyVersionConflict(string directory, string assembly, string parentAssembly, int problemId) + { + var conflict1 = CreateAssemblyVersionConflict(directory, assembly, parentAssembly, problemId); + var conflict2 = new AssemblyVersionConflict().Parse(conflict1.FormatRecord()); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , null, int.MinValue)] + [InlineData("", "", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", "MyParentAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "My.Longer.ParentAssembly", 2000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanContrastAssemblyVersionConflict(string directory, string assembly, string parentAssembly, int problemId) + { + var conflict1 = CreateAssemblyVersionConflict(directory, assembly, parentAssembly, problemId); + var conflict2 = CreateAssemblyVersionConflict(GetRandomString(), assembly, parentAssembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateAssemblyVersionConflict(directory, GetRandomString(), parentAssembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateAssemblyVersionConflict(directory, assembly, GetRandomString(), problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateAssemblyVersionConflict(directory, assembly, parentAssembly, Random.Next()); + Assert.False(conflict1.Match(conflict2)); + } + + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , int.MinValue)] + [InlineData("", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", 1000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", 0)] + public void CanMatchExtraAssembly(string directory, string assembly, int problemId) + { + var conflict1 = CreateExtraAssembly(directory, assembly, problemId); + var conflict2 = CreateExtraAssembly(directory, assembly, problemId, true); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("dir1/dir2/file/", "MyAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", 1000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", 0)] + public void CanRoundTripExtraAssembly(string directory, string assembly, int problemId) + { + var conflict1 = CreateExtraAssembly(directory, assembly, problemId); + var conflict2 = new ExtraAssembly().Parse(conflict1.FormatRecord()); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , int.MinValue)] + [InlineData("", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", 1000)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", 0)] + public void CanContrastExtraAssembly(string directory, string assembly, int problemId) + { + var conflict1 = CreateExtraAssembly(directory, assembly, problemId); + var conflict2 = CreateExtraAssembly(GetRandomString(), assembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateExtraAssembly(directory, GetRandomString(), problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateExtraAssembly(directory, assembly, Random.Next()); + Assert.False(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , "1.0", null, int.MinValue)] + [InlineData("", "", "2.0", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", "1.9.9", "MyRefAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "9.9.999.9999", "My.Longer.Ref.Assembly", 100)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "1.2.3.4","ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanMatchMissingAssembly(string directory, string assembly, string version, string refAssembly, + int problemId) + { + var conflict1 = CreateMissingAssembly(directory, assembly, version, refAssembly, problemId); + var conflict2 = CreateMissingAssembly(directory, assembly, version, refAssembly, problemId, true); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("dir1/dir2/file/", "MyAssembly", "1.9.9", "MyRefAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "9.9.999.9999", "My.Longer.Ref.Assembly", 100)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "1.2.3.4","ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanRoundTripMissingAssembly(string directory, string assembly, string version, string refAssembly, + int problemId) + { + var conflict1 = CreateMissingAssembly(directory, assembly, version, refAssembly, problemId); + var conflict2 = new MissingAssembly().Parse(conflict1.FormatRecord()); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("", null , "1.0", null, int.MinValue)] + [InlineData("", "", "2.0", "", int.MinValue)] + [InlineData("dir1/dir2/file/", "MyAssembly", "1.9.9", "MyRefAssembly", int.MaxValue)] + [InlineData("\\dir1\\dir2\\dir3\\", "My.Longer.Assembly", "9.9.999.9999", "My.Longer.Ref.Assembly", 100)] + [InlineData("\\dir1\\dir2\\啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "1.2.3.4","ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanContrastMissingAssembly(string directory, string assembly, string version, string refAssembly, + int problemId) + { + var conflict1 = CreateMissingAssembly(directory, assembly, version, refAssembly, problemId); + var conflict2 = CreateMissingAssembly(GetRandomString(), assembly, version, refAssembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateMissingAssembly(directory, GetRandomString(), version, refAssembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateMissingAssembly(directory, assembly, GetRandomVersion().ToString(), refAssembly, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateMissingAssembly(directory, assembly, version, GetRandomString(), problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateMissingAssembly(directory, assembly, version, refAssembly, Random.Next()); + Assert.False(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData(null, "1.0", int.MinValue)] + [InlineData("", "1.0.2", int.MinValue)] + [InlineData("MyAssembly", "9.99.999.9999", int.MaxValue)] + [InlineData("My.Longer.Assembly", "0.0.0.1", 2000)] + [InlineData("㙉㙊䵯䵰䶴䶵", "0.0.1", 0)] + public void CanMatchSharedAssemblyConflict(string assembly, string version, int problemId) + { + var conflict1 = CreateSharedAssemblyConflict(assembly, version, problemId); + var conflict2 = CreateSharedAssemblyConflict(assembly, version, problemId, true); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData("MyAssembly", "9.99.999.9999", int.MaxValue)] + [InlineData("My.Longer.Assembly", "0.0.0.1", 2000)] + [InlineData("㙉㙊䵯䵰䶴䶵", "0.0.1", 0)] + public void CanRoundTripSharedAssemblyConflict(string assembly, string version, int problemId) + { + var conflict1 = CreateSharedAssemblyConflict(assembly, version, problemId); + var conflict2 = new SharedAssemblyConflict().Parse(conflict1.FormatRecord()); + Assert.True(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData(null, "1.0", int.MinValue)] + [InlineData("", "1.0.2", int.MinValue)] + [InlineData("MyAssembly", "9.99.999.9999", int.MaxValue)] + [InlineData("My.Longer.Assembly", "0.0.0.1", 2000)] + [InlineData("㙉㙊䵯䵰䶴䶵", "0.0.1", 0)] + public void CanContrastSharedAssemblyConflict(string assembly, string version, int problemId) + { + var conflict1 = CreateSharedAssemblyConflict(assembly, version, problemId); + var conflict2 = CreateSharedAssemblyConflict(GetRandomString(), version, problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateSharedAssemblyConflict(assembly, GetRandomVersion().ToString(), problemId); + Assert.False(conflict1.Match(conflict2)); + conflict2 = CreateSharedAssemblyConflict(assembly, version, Random.Next()); + Assert.False(conflict1.Match(conflict2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData(null, null, null, int.MinValue)] + [InlineData("", "", "", int.MinValue)] + [InlineData( "MyAssembly", "MyHelpFile", "MyTarget", int.MaxValue)] + [InlineData("My.Longer.Assembly", "My.Longer.Helpfile", "My.Longer.Target", 100)] + [InlineData("啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanMatchHelpIssue(string assembly, string helpFile, string target, int problemId) + { + var help1 = CreateHelpIssue(assembly, helpFile, target, problemId); + var help2 = CreateHelpIssue(assembly, helpFile, target, problemId, true); + Assert.True(help1.Match(help2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData( "MyAssembly", "MyHelpFile", "MyTarget", int.MaxValue)] + [InlineData("My.Longer.Assembly", "My.Longer.Helpfile", "My.Longer.Target", 100)] + [InlineData("啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanRoundTripHelpIssue(string assembly, string helpFile, string target, int problemId) + { + var help1 = CreateHelpIssue(assembly, helpFile, target, problemId); + var help2 = new HelpIssue().Parse(help1.FormatRecord()); + Assert.True(help1.Match(help2)); + } + + [Theory] + [Trait(Category.AcceptanceType, Category.CheckIn)] + [InlineData(null, null, null, int.MinValue)] + [InlineData("", "", "", int.MinValue)] + [InlineData( "MyAssembly", "MyHelpFile", "MyTarget", int.MaxValue)] + [InlineData("My.Longer.Assembly", "My.Longer.Helpfile", "My.Longer.Target", 100)] + [InlineData("啊齄丂狛狜隣郎隣兀﨩", "㙉㙊䵯䵰䶴䶵", "ᠠᡷᢀᡨᡩᡪᡫ", 0)] + public void CanContrastHelpIssue(string assembly, string helpFile, string target, int problemId) + { + var help1 = CreateHelpIssue(assembly, helpFile, target, problemId); + var help2 = CreateHelpIssue(GetRandomString(), helpFile, target, problemId); + Assert.False(help1.Match(help2)); + help2 = CreateHelpIssue(assembly, GetRandomString(), target, problemId); + Assert.False(help1.Match(help2)); + help2 = CreateHelpIssue(assembly, helpFile, GetRandomString(), problemId); + Assert.False(help1.Match(help2)); + help2 = CreateHelpIssue(assembly, helpFile, target, Random.Next()); + Assert.False(help1.Match(help2)); + } + + } +} diff --git a/tools/StaticAnalysis/StaticAnalysis.Test/Properties/AssemblyInfo.cs b/tools/StaticAnalysis/StaticAnalysis.Test/Properties/AssemblyInfo.cs new file mode 100644 index 000000000000..c4a47c3a7e47 --- /dev/null +++ b/tools/StaticAnalysis/StaticAnalysis.Test/Properties/AssemblyInfo.cs @@ -0,0 +1,36 @@ +using System.Reflection; +using System.Runtime.CompilerServices; +using System.Runtime.InteropServices; + +// General Information about an assembly is controlled through the following +// set of attributes. Change these attribute values to modify the information +// associated with an assembly. +[assembly: AssemblyTitle("StaticAnalysis.Test")] +[assembly: AssemblyDescription("")] +[assembly: AssemblyConfiguration("")] +[assembly: AssemblyCompany("")] +[assembly: AssemblyProduct("StaticAnalysis.Test")] +[assembly: AssemblyCopyright("Copyright © 2016")] +[assembly: AssemblyTrademark("")] +[assembly: AssemblyCulture("")] + +// Setting ComVisible to false makes the types in this assembly not visible +// to COM components. If you need to access a type in this assembly from +// COM, set the ComVisible attribute to true on that type. +[assembly: ComVisible(false)] + +// The following GUID is for the ID of the typelib if this project is exposed to COM +[assembly: Guid("f74b11e2-939c-4a80-a325-9d88d0171861")] + +// Version information for an assembly consists of the following four values: +// +// Major Version +// Minor Version +// Build Number +// Revision +// +// You can specify all the values or you can default the Build and Revision Numbers +// by using the '*' as shown below: +// [assembly: AssemblyVersion("1.0.*")] +[assembly: AssemblyVersion("1.0.0.0")] +[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/tools/StaticAnalysis/StaticAnalysis.Test/StaticAnalysis.Test.csproj b/tools/StaticAnalysis/StaticAnalysis.Test/StaticAnalysis.Test.csproj new file mode 100644 index 000000000000..90c8861e7f02 --- /dev/null +++ b/tools/StaticAnalysis/StaticAnalysis.Test/StaticAnalysis.Test.csproj @@ -0,0 +1,92 @@ + + + + + + + Debug + AnyCPU + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F} + Library + Properties + StaticAnalysis.Test + StaticAnalysis.Test + v4.5 + 512 + ba98ab34 + + + true + full + false + bin\Debug\ + DEBUG;TRACE + prompt + 4 + + + pdbonly + true + bin\Release\ + TRACE + prompt + 4 + + + + + + + + + + + ..\packages\xunit.abstractions.2.0.0\lib\net35\xunit.abstractions.dll + True + + + ..\packages\xunit.assert.2.1.0\lib\portable-net45+win8+wp8+wpa81\xunit.assert.dll + True + + + ..\packages\xunit.extensibility.core.2.1.0\lib\portable-net45+win8+wp8+wpa81\xunit.core.dll + True + + + ..\packages\xunit.extensibility.execution.2.1.0\lib\net45\xunit.execution.desktop.dll + True + + + + + + + + + + {68384b59-ba0c-4b7b-b3f6-9c7988296c16} + StaticAnalysis + + + + + + + + + + + + This project references NuGet package(s) that are missing on this computer. Enable NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}. + + + + + + \ No newline at end of file diff --git a/tools/StaticAnalysis/StaticAnalysis.Test/packages.config b/tools/StaticAnalysis/StaticAnalysis.Test/packages.config new file mode 100644 index 000000000000..dcbf45edf06b --- /dev/null +++ b/tools/StaticAnalysis/StaticAnalysis.Test/packages.config @@ -0,0 +1,10 @@ + + + + + + + + + + \ No newline at end of file diff --git a/tools/StaticAnalysis/StaticAnalysis.csproj b/tools/StaticAnalysis/StaticAnalysis.csproj index 21a772b5b05c..68443e550f63 100644 --- a/tools/StaticAnalysis/StaticAnalysis.csproj +++ b/tools/StaticAnalysis/StaticAnalysis.csproj @@ -46,7 +46,7 @@ - + @@ -72,6 +72,18 @@ + + PreserveNewest + + + PreserveNewest + + + PreserveNewest + + + PreserveNewest + diff --git a/tools/StaticAnalysis/StaticAnalysis.sln b/tools/StaticAnalysis/StaticAnalysis.sln index ff18b9d7cfe9..08fc59506fdc 100644 --- a/tools/StaticAnalysis/StaticAnalysis.sln +++ b/tools/StaticAnalysis/StaticAnalysis.sln @@ -3,7 +3,11 @@ Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 2013 VisualStudioVersion = 12.0.40629.0 MinimumVisualStudioVersion = 10.0.40219.1 -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Static Analysis", "StaticAnalysis.csproj", "{68384B59-BA0C-4B7B-B3F6-9C7988296C16}" +Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "StaticAnalysis", "StaticAnalysis.csproj", "{68384B59-BA0C-4B7B-B3F6-9C7988296C16}" +EndProject +Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Test", "Test", "{865C472B-4679-4B71-AA4B-B85283F3475D}" +EndProject +Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "StaticAnalysis.Test", "StaticAnalysis.Test\StaticAnalysis.Test.csproj", "{A034BE7F-0CD8-4A03-85B3-44CC2E58B86F}" EndProject Global GlobalSection(SolutionConfigurationPlatforms) = preSolution @@ -15,8 +19,15 @@ Global {68384B59-BA0C-4B7B-B3F6-9C7988296C16}.Debug|Any CPU.Build.0 = Debug|Any CPU {68384B59-BA0C-4B7B-B3F6-9C7988296C16}.Release|Any CPU.ActiveCfg = Release|Any CPU {68384B59-BA0C-4B7B-B3F6-9C7988296C16}.Release|Any CPU.Build.0 = Release|Any CPU + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F}.Debug|Any CPU.Build.0 = Debug|Any CPU + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F}.Release|Any CPU.ActiveCfg = Release|Any CPU + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F}.Release|Any CPU.Build.0 = Release|Any CPU EndGlobalSection GlobalSection(SolutionProperties) = preSolution HideSolutionNode = FALSE EndGlobalSection + GlobalSection(NestedProjects) = preSolution + {A034BE7F-0CD8-4A03-85B3-44CC2E58B86F} = {865C472B-4679-4B71-AA4B-B85283F3475D} + EndGlobalSection EndGlobal