diff --git a/src/Common/Commands.Common.Authentication.Test/Commands.Common.Authentication.Test.csproj b/src/Common/Commands.Common.Authentication.Test/Commands.Common.Authentication.Test.csproj index 763ebd8ca5d5..bd29d9593b1f 100644 --- a/src/Common/Commands.Common.Authentication.Test/Commands.Common.Authentication.Test.csproj +++ b/src/Common/Commands.Common.Authentication.Test/Commands.Common.Authentication.Test.csproj @@ -84,7 +84,7 @@ True - ..\..\packages\Moq.4.2.1409.1722\lib\net40\Moq.dll + ..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/Common/Commands.Common.Authentication.Test/packages.config b/src/Common/Commands.Common.Authentication.Test/packages.config index 6933da5a807e..42e529595fb1 100644 --- a/src/Common/Commands.Common.Authentication.Test/packages.config +++ b/src/Common/Commands.Common.Authentication.Test/packages.config @@ -12,7 +12,7 @@ - + diff --git a/src/Common/Commands.Common/Commands.Common.csproj b/src/Common/Commands.Common/Commands.Common.csproj index 93ff04d6eee5..6cccbf7d33ae 100644 --- a/src/Common/Commands.Common/Commands.Common.csproj +++ b/src/Common/Commands.Common/Commands.Common.csproj @@ -159,7 +159,6 @@ - diff --git a/src/Common/Commands.Common/ServiceClientTracingInterceptor.cs b/src/Common/Commands.Common/ServiceClientTracingInterceptor.cs deleted file mode 100644 index 3f23d99c23e2..000000000000 --- a/src/Common/Commands.Common/ServiceClientTracingInterceptor.cs +++ /dev/null @@ -1,79 +0,0 @@ -// ---------------------------------------------------------------------------------- -// -// 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 Microsoft.Rest; -//using System; -//using System.Collections.Concurrent; -//using System.Collections.Generic; -//using System.Diagnostics; -//using System.Linq; -//using System.Text; -//using System.Threading.Tasks; -//namespace Microsoft.WindowsAzure.Commands.Common -//{ -// class ServiceClientTracingInterceptor : IServiceClientTracingInterceptor -// { -// public ServiceClientTracingInterceptor(ConcurrentQueue queue) -// { -// MessageQueue = queue; -// } - -// public ConcurrentQueue MessageQueue { get; private set; } - -// public void Configuration(string source, string name, string value) -// { -// // Ignore -// } - -// public void EnterMethod(string invocationId, object instance, string method, IDictionary parameters) -// { -// // Ignore -// } - -// public void ExitMethod(string invocationId, object returnValue) -// { -// // Ignore -// } - -// public void Information(string message) -// { -// MessageQueue.CheckAndEnqueue(message); -// } - -// public void ReceiveResponse(string invocationId, System.Net.Http.HttpResponseMessage response) -// { -// string responseAsString = response == null ? string.Empty : response.AsFormattedString(); -// MessageQueue.CheckAndEnqueue(responseAsString); -// } - -// public void SendRequest(string invocationId, System.Net.Http.HttpRequestMessage request) -// { -// string requestAsString = request == null ? string.Empty : request.AsFormattedString(); -// MessageQueue.CheckAndEnqueue(requestAsString); -// } - -// public void TraceError(string invocationId, Exception exception) -// { -// // Ignore -// } - -// public static void RemoveTracingInterceptor(ServiceClientTracingInterceptor interceptor) -// { -// if (interceptor != null) -// { -// ServiceClientTracing.RemoveTracingInterceptor(interceptor); -// } -// } -// } -//} diff --git a/src/Common/Commands.Common/TestMockSupport.cs b/src/Common/Commands.Common/TestMockSupport.cs index 6e2a38c518a9..f805acfe35f3 100644 --- a/src/Common/Commands.Common/TestMockSupport.cs +++ b/src/Common/Commands.Common/TestMockSupport.cs @@ -29,6 +29,10 @@ public static void Delay(int milliSeconds) { System.Threading.Thread.Sleep(milliSeconds); } + else + { + System.Threading.Thread.Yield(); + } } public static void Delay(TimeSpan duration) @@ -37,6 +41,10 @@ public static void Delay(TimeSpan duration) { System.Threading.Thread.Sleep(duration); } + else + { + System.Threading.Thread.Yield(); + } } } } diff --git a/src/Common/Storage/Azure.Storage.psd1 b/src/Common/Storage/Azure.Storage.psd1 index 6ce84f003c65..11e86ba81dd9 100644 --- a/src/Common/Storage/Azure.Storage.psd1 +++ b/src/Common/Storage/Azure.Storage.psd1 @@ -91,6 +91,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } \ No newline at end of file diff --git a/src/Common/Storage/Commands.Storage/Microsoft.WindowsAzure.Commands.Storage.dll-Help.psd1 b/src/Common/Storage/Commands.Storage/Microsoft.WindowsAzure.Commands.Storage.dll-Help.psd1 index 19c0010da379..9e0747043af0 100644 --- a/src/Common/Storage/Commands.Storage/Microsoft.WindowsAzure.Commands.Storage.dll-Help.psd1 +++ b/src/Common/Storage/Commands.Storage/Microsoft.WindowsAzure.Commands.Storage.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/ApiManagement/AzureRM.ApiManagement.psd1 b/src/ResourceManager/ApiManagement/AzureRM.ApiManagement.psd1 index 04e13b99af0c..e6d8d97586cd 100644 --- a/src/ResourceManager/ApiManagement/AzureRM.ApiManagement.psd1 +++ b/src/ResourceManager/ApiManagement/AzureRM.ApiManagement.psd1 @@ -84,6 +84,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/ApiManagement/Commands.ApiManagement.ServiceManagement/Microsoft.Azure.Commands.ApiManagement.ServiceManagement.dll-help.psd1 b/src/ResourceManager/ApiManagement/Commands.ApiManagement.ServiceManagement/Microsoft.Azure.Commands.ApiManagement.ServiceManagement.dll-help.psd1 index 1ebd2d8198ef..9798b213fba8 100644 --- a/src/ResourceManager/ApiManagement/Commands.ApiManagement.ServiceManagement/Microsoft.Azure.Commands.ApiManagement.ServiceManagement.dll-help.psd1 +++ b/src/ResourceManager/ApiManagement/Commands.ApiManagement.ServiceManagement/Microsoft.Azure.Commands.ApiManagement.ServiceManagement.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/ApiManagement/Commands.ApiManagement/Microsoft.Azure.Commands.ApiManagement.dll-help.psd1 b/src/ResourceManager/ApiManagement/Commands.ApiManagement/Microsoft.Azure.Commands.ApiManagement.dll-help.psd1 index 0b716c4ee335..b89a7636be8a 100644 --- a/src/ResourceManager/ApiManagement/Commands.ApiManagement/Microsoft.Azure.Commands.ApiManagement.dll-help.psd1 +++ b/src/ResourceManager/ApiManagement/Commands.ApiManagement/Microsoft.Azure.Commands.ApiManagement.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Automation/AzureRM.Automation.psd1 b/src/ResourceManager/Automation/AzureRM.Automation.psd1 index da7b031a8df0..e3911c126bf1 100644 --- a/src/ResourceManager/Automation/AzureRM.Automation.psd1 +++ b/src/ResourceManager/Automation/AzureRM.Automation.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj b/src/ResourceManager/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj index 496ed4aefcf6..baac20f06cec 100644 --- a/src/ResourceManager/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj +++ b/src/ResourceManager/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj @@ -107,9 +107,9 @@ False ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Automation/Commands.Automation.Test/packages.config b/src/ResourceManager/Automation/Commands.Automation.Test/packages.config index 47669e1eb6e2..5bacf249b68a 100644 --- a/src/ResourceManager/Automation/Commands.Automation.Test/packages.config +++ b/src/ResourceManager/Automation/Commands.Automation.Test/packages.config @@ -14,7 +14,7 @@ - + diff --git a/src/ResourceManager/Automation/Commands.Automation/Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.psd1 b/src/ResourceManager/Automation/Commands.Automation/Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.psd1 index 10184949a318..c9d3f9ede628 100644 --- a/src/ResourceManager/Automation/Commands.Automation/Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.psd1 +++ b/src/ResourceManager/Automation/Commands.Automation/Microsoft.Azure.Commands.ResourceManager.Automation.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureBackup/AzureRM.Backup.psd1 b/src/ResourceManager/AzureBackup/AzureRM.Backup.psd1 index 019005cb673d..56fd0e5e3098 100644 --- a/src/ResourceManager/AzureBackup/AzureRM.Backup.psd1 +++ b/src/ResourceManager/AzureBackup/AzureRM.Backup.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureBackup/Commands.AzureBackup/Microsoft.Azure.Commands.AzureBackup.dll-help.psd1 b/src/ResourceManager/AzureBackup/Commands.AzureBackup/Microsoft.Azure.Commands.AzureBackup.dll-help.psd1 index 0a5fbe79cd1d..cbb91314c761 100644 --- a/src/ResourceManager/AzureBackup/Commands.AzureBackup/Microsoft.Azure.Commands.AzureBackup.dll-help.psd1 +++ b/src/ResourceManager/AzureBackup/Commands.AzureBackup/Microsoft.Azure.Commands.AzureBackup.dll-help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureBatch/AzureRM.Batch.psd1 b/src/ResourceManager/AzureBatch/AzureRM.Batch.psd1 index 09fce5f17afa..ba5640504fe7 100644 --- a/src/ResourceManager/AzureBatch/AzureRM.Batch.psd1 +++ b/src/ResourceManager/AzureBatch/AzureRM.Batch.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureBatch/Commands.Batch.Test/Commands.Batch.Test.csproj b/src/ResourceManager/AzureBatch/Commands.Batch.Test/Commands.Batch.Test.csproj index c544dc9f90e4..061d92086ad1 100644 --- a/src/ResourceManager/AzureBatch/Commands.Batch.Test/Commands.Batch.Test.csproj +++ b/src/ResourceManager/AzureBatch/Commands.Batch.Test/Commands.Batch.Test.csproj @@ -128,7 +128,7 @@ ..\..\..\packages\WindowsAzure.Storage.6.1.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/AzureBatch/Commands.Batch.Test/packages.config b/src/ResourceManager/AzureBatch/Commands.Batch.Test/packages.config index cb061576d145..12de06b1b786 100644 --- a/src/ResourceManager/AzureBatch/Commands.Batch.Test/packages.config +++ b/src/ResourceManager/AzureBatch/Commands.Batch.Test/packages.config @@ -23,7 +23,7 @@ - + diff --git a/src/ResourceManager/AzureStackAdmin/AzureRM.AzureStackAdmin.psd1 b/src/ResourceManager/AzureStackAdmin/AzureRM.AzureStackAdmin.psd1 index c76520b0d750..0d86501b0e7d 100644 --- a/src/ResourceManager/AzureStackAdmin/AzureRM.AzureStackAdmin.psd1 +++ b/src/ResourceManager/AzureStackAdmin/AzureRM.AzureStackAdmin.psd1 @@ -81,6 +81,27 @@ ModuleList = @() # FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Commands.AzureStackAdmin.Test.csproj b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Commands.AzureStackAdmin.Test.csproj index 7f0b67f3b5b6..e3292fe3d654 100644 --- a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Commands.AzureStackAdmin.Test.csproj +++ b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Commands.AzureStackAdmin.Test.csproj @@ -116,9 +116,9 @@ False ..\..\..\packages\WindowsAzure.Storage.4.3.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/Commands.AzureStackAdmin.Test.Common.csproj b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/Commands.AzureStackAdmin.Test.Common.csproj index 6eea4e76debf..11e375f946a7 100644 --- a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/Commands.AzureStackAdmin.Test.Common.csproj +++ b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/Commands.AzureStackAdmin.Test.Common.csproj @@ -98,9 +98,9 @@ False ..\..\..\..\packages\Microsoft.Bcl.Async.1.0.168\lib\net40\Microsoft.Threading.Tasks.Extensions.Desktop.dll - + False - ..\..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/packages.config b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/packages.config index aef7658d8cca..76c475ed3c3d 100644 --- a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/packages.config +++ b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/Common/packages.config @@ -15,7 +15,7 @@ - + diff --git a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/packages.config b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/packages.config index 464862b29fbe..ed145a19db1f 100644 --- a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/packages.config +++ b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin.Test/packages.config @@ -16,7 +16,7 @@ - + diff --git a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin/Microsoft.AzureStack.Commands.dll-help.psd1 b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin/Microsoft.AzureStack.Commands.dll-help.psd1 index 7bd34f5212b2..068c23a23637 100644 --- a/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin/Microsoft.AzureStack.Commands.dll-help.psd1 +++ b/src/ResourceManager/AzureStackAdmin/Commands.AzureStackAdmin/Microsoft.AzureStack.Commands.dll-help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureStackStorage/AzureRM.AzureStackStorage.psd1 b/src/ResourceManager/AzureStackStorage/AzureRM.AzureStackStorage.psd1 index 45f60d0d8f78..183974514663 100644 --- a/src/ResourceManager/AzureStackStorage/AzureRM.AzureStackStorage.psd1 +++ b/src/ResourceManager/AzureStackStorage/AzureRM.AzureStackStorage.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/Commands.AzureStackStorage.Test.csproj b/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/Commands.AzureStackStorage.Test.csproj index 23bb9830fc39..153e6ab00306 100644 --- a/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/Commands.AzureStackStorage.Test.csproj +++ b/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/Commands.AzureStackStorage.Test.csproj @@ -107,9 +107,9 @@ False ..\..\..\packages\WindowsAzure.Storage.4.3.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/packages.config b/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/packages.config index 45521fde5af0..ff450e8e28d4 100644 --- a/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/packages.config +++ b/src/ResourceManager/AzureStackStorage/Commands.AzureStackStorage.Tests/packages.config @@ -17,7 +17,7 @@ - + diff --git a/src/ResourceManager/Common/Commands.ResourceManager.Common/AzureRMCmdlet.cs b/src/ResourceManager/Common/Commands.ResourceManager.Common/AzureRMCmdlet.cs index adc3a8611093..2a2f152250c4 100644 --- a/src/ResourceManager/Common/Commands.ResourceManager.Common/AzureRMCmdlet.cs +++ b/src/ResourceManager/Common/Commands.ResourceManager.Common/AzureRMCmdlet.cs @@ -204,6 +204,7 @@ protected override void LogCmdletEndInvocationInfo() protected override void SetupDebuggingTraces() { + ServiceClientTracing.IsEnabled = true; base.SetupDebuggingTraces(); _serviceClientTracingInterceptor = _serviceClientTracingInterceptor ?? new ServiceClientTracingInterceptor(DebugMessages); diff --git a/src/ResourceManager/Common/Commands.ResourceManager.Common/ServiceClientTracingInterceptor.cs b/src/ResourceManager/Common/Commands.ResourceManager.Common/ServiceClientTracingInterceptor.cs index 9bdb0565cbe7..e29a55fae86a 100644 --- a/src/ResourceManager/Common/Commands.ResourceManager.Common/ServiceClientTracingInterceptor.cs +++ b/src/ResourceManager/Common/Commands.ResourceManager.Common/ServiceClientTracingInterceptor.cs @@ -17,6 +17,8 @@ using System.Collections.Concurrent; using System.Collections.Generic; using Microsoft.WindowsAzure.Commands.Common; +using Microsoft.WindowsAzure.Commands.Utilities.Common; + namespace Microsoft.Azure.Commands.ResourceManager.Common { public class ServiceClientTracingInterceptor : IServiceClientTracingInterceptor @@ -50,13 +52,13 @@ public void Information(string message) public void ReceiveResponse(string invocationId, System.Net.Http.HttpResponseMessage response) { - string responseAsString = response == null ? string.Empty : response.AsFormattedString(); + string responseAsString = response == null ? string.Empty : GeneralUtilities.GetLog(response); MessageQueue.CheckAndEnqueue(responseAsString); } public void SendRequest(string invocationId, System.Net.Http.HttpRequestMessage request) { - string requestAsString = request == null ? string.Empty : request.AsFormattedString(); + string requestAsString = request == null ? string.Empty : GeneralUtilities.GetLog(request); MessageQueue.CheckAndEnqueue(requestAsString); } diff --git a/src/ResourceManager/Compute/AzureRM.Compute.psd1 b/src/ResourceManager/Compute/AzureRM.Compute.psd1 index c3ec93d57608..3951c9594dca 100644 --- a/src/ResourceManager/Compute/AzureRM.Compute.psd1 +++ b/src/ResourceManager/Compute/AzureRM.Compute.psd1 @@ -89,6 +89,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Compute/Commands.Compute.Test/Commands.Compute.Test.csproj b/src/ResourceManager/Compute/Commands.Compute.Test/Commands.Compute.Test.csproj index 2522f11ad8f5..ffe17dcb32d9 100644 --- a/src/ResourceManager/Compute/Commands.Compute.Test/Commands.Compute.Test.csproj +++ b/src/ResourceManager/Compute/Commands.Compute.Test/Commands.Compute.Test.csproj @@ -117,9 +117,9 @@ False ..\..\..\packages\Microsoft.Bcl.Async.1.0.168\lib\net40\Microsoft.Threading.Tasks.Extensions.Desktop.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Compute/Commands.Compute.Test/packages.config b/src/ResourceManager/Compute/Commands.Compute.Test/packages.config index 1d00343fd1e0..b4bab5e1391e 100644 --- a/src/ResourceManager/Compute/Commands.Compute.Test/packages.config +++ b/src/ResourceManager/Compute/Commands.Compute.Test/packages.config @@ -19,7 +19,7 @@ - + diff --git a/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js b/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js index a947eaba8618..bdb825056917 100644 --- a/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js +++ b/src/ResourceManager/Compute/Commands.Compute/Generated/cli.js @@ -212,10 +212,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.createOrUpdate(resourceGroupName, name, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); - var virtualMachineScaleSetsCreateOrUpdatecreateOrUpdateParameters2 = virtualMachineScaleSetsCreateOrUpdate.category('create-or-update-parameters') - .description($('Commands to generate parameter input file for your virtual machine scale sets.')); + var virtualMachineScaleSetsCreateOrUpdatecreateOrUpdateParameters2 = virtualMachineScaleSetsCreateOrUpdate.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); virtualMachineScaleSetsCreateOrUpdatecreateOrUpdateParameters2.command('generate') .description($('Generate virtualMachineScaleSetsCreateOrUpdate parameter string or files.')) .usage('[options]') @@ -277,14 +279,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set virtual-machine-scale-set + //config set virtual-machine-scale-set var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('virtual-machine-scale-set') - .description($('Commands to set/remove/add virtual-machine-scale-set of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.command('set') - .description($('Set virtual-machine-scale-set in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet0.command('virtual-machine-scale-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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -413,14 +415,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove virtual-machine-scale-set + //config remove virtual-machine-scale-set var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('virtual-machine-scale-set') - .description($('Commands to set/remove/add virtual-machine-scale-set of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.command('remove') - .description($('Remove virtual-machine-scale-set in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet1.command('virtual-machine-scale-set') + .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.')) .option('--sku', $('Remove the sku value.')) @@ -497,14 +499,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add virtual-machine-scale-set + //config add virtual-machine-scale-set var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('virtual-machine-scale-set') - .description($('Commands to set/remove/add virtual-machine-scale-set of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.command('add') - .description($('Add virtual-machine-scale-set in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineScaleSet2.command('virtual-machine-scale-set') + .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.')) .option('--key ', $('The JSON key.')) @@ -637,14 +639,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set sku + //config set sku var catparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSku0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = parametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('sku') - .description($('Commands to set/remove/add sku of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSku0.command('set') - .description($('Set sku in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSku0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsSku0 = parametersCreateOrUpdateVirtualMachineScaleSetsSku0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsSku0.command('sku') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -708,14 +710,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove sku + //config remove sku var catparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSku1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = parametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('sku') - .description($('Commands to set/remove/add sku of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1.command('remove') - .description($('Remove sku in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSku1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1 = parametersCreateOrUpdateVirtualMachineScaleSetsSku1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsSku1.command('sku') + .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.')) .option('--name', $('Remove the name value.')) @@ -762,14 +764,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add sku + //config add sku var catparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSku2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = parametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('sku') - .description($('Commands to set/remove/add sku of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSku2.command('add') - .description($('Add sku in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSku2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsSku2 = parametersCreateOrUpdateVirtualMachineScaleSetsSku2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsSku2.command('sku') + .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.')) .option('--key ', $('The JSON key.')) @@ -837,14 +839,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set upgrade-policy + //config set upgrade-policy var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('upgrade-policy') - .description($('Commands to set/remove/add upgrade-policy of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.command('set') - .description($('Set upgrade-policy in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy0.command('upgrade-policy') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -885,14 +887,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove upgrade-policy + //config remove upgrade-policy var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('upgrade-policy') - .description($('Commands to set/remove/add upgrade-policy of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.command('remove') - .description($('Remove upgrade-policy in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy1.command('upgrade-policy') + .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.')) .option('--mode', $('Remove the mode value.')) @@ -929,14 +931,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add upgrade-policy + //config add upgrade-policy var catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('upgrade-policy') - .description($('Commands to set/remove/add upgrade-policy of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.command('add') - .description($('Add upgrade-policy in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = catparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2 = parametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsUpgradePolicy2.command('upgrade-policy') + .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.')) .option('--key ', $('The JSON key.')) @@ -981,95 +983,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set virtual-machine-profile - var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0.category('virtual-machine-profile') - .description($('Commands to set/remove/add virtual-machine-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile0.command('set') - .description($('Set virtual-machine-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--os-profile ', $('Set the os-profile value.')) - .option('--storage-profile ', $('Set the storage-profile value.')) - .option('--network-profile ', $('Set the network-profile value.')) - .option('--extension-profile ', $('Set the extension-profile value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile'; - var paramPath = options.path + '/' + 'osProfile'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.osProfile) { - if (options.parse && options.osProfile) { - options.osProfile = JSON.parse(options.osProfile); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.osProfile}]); - } - paramPath = options.path + '/' + 'storageProfile'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.storageProfile) { - if (options.parse && options.storageProfile) { - options.storageProfile = JSON.parse(options.storageProfile); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.storageProfile}]); - } - paramPath = options.path + '/' + 'networkProfile'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.networkProfile) { - if (options.parse && options.networkProfile) { - options.networkProfile = JSON.parse(options.networkProfile); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.networkProfile}]); - } - paramPath = options.path + '/' + 'extensionProfile'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.extensionProfile) { - if (options.parse && options.extensionProfile) { - options.extensionProfile = JSON.parse(options.extensionProfile); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.extensionProfile}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove virtual-machine-profile + //config remove virtual-machine-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('virtual-machine-profile') - .description($('Commands to set/remove/add virtual-machine-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.command('remove') - .description($('Remove virtual-machine-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile1.command('virtual-machine-profile') + .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.')) .option('--os-profile', $('Remove the os-profile value.')) @@ -1121,14 +1042,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add virtual-machine-profile + //config add virtual-machine-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('virtual-machine-profile') - .description($('Commands to set/remove/add virtual-machine-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.command('add') - .description($('Add virtual-machine-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsVirtualMachineProfile2.command('virtual-machine-profile') + .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.')) .option('--key ', $('The JSON key.')) @@ -1206,14 +1127,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set os-profile + //config set os-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('os-profile') - .description($('Commands to set/remove/add os-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.command('set') - .description($('Set os-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile0.command('os-profile') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -1320,14 +1241,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove os-profile + //config remove os-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('os-profile') - .description($('Commands to set/remove/add os-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.command('remove') - .description($('Remove os-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile1.command('os-profile') + .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.')) .option('--computer-name-prefix', $('Remove the computer-name-prefix value.')) @@ -1394,14 +1315,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add os-profile + //config add os-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('os-profile') - .description($('Commands to set/remove/add os-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.command('add') - .description($('Add os-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsOsProfile2.command('os-profile') + .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.')) .option('--key ', $('The JSON key.')) @@ -1512,14 +1433,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set windows-configuration + //config set windows-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('windows-configuration') - .description($('Commands to set/remove/add windows-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.command('set') - .description($('Set windows-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration0.command('windows-configuration') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -1606,14 +1527,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove windows-configuration + //config remove windows-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('windows-configuration') - .description($('Commands to set/remove/add windows-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.command('remove') - .description($('Remove windows-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration1.command('windows-configuration') + .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.')) .option('--provision-vm-agent', $('Remove the provision-vm-agent value.')) @@ -1670,14 +1591,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add windows-configuration + //config add windows-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('windows-configuration') - .description($('Commands to set/remove/add windows-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.command('add') - .description($('Add windows-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsWindowsConfiguration2.command('windows-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -1768,14 +1689,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set additional-unattend-content + //config set additional-unattend-content var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('additional-unattend-content') - .description($('Commands to set/remove/add additional-unattend-content of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.command('set') - .description($('Set additional-unattend-content in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent0.command('additional-unattend-content') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1854,14 +1775,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove additional-unattend-content + //config remove additional-unattend-content var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('additional-unattend-content') - .description($('Commands to set/remove/add additional-unattend-content of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.command('remove') - .description($('Remove additional-unattend-content in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent1.command('additional-unattend-content') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1914,14 +1835,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add additional-unattend-content + //config add additional-unattend-content var catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('additional-unattend-content') - .description($('Commands to set/remove/add additional-unattend-content of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.command('add') - .description($('Add additional-unattend-content in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = catparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2 = parametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsAdditionalUnattendContent2.command('additional-unattend-content') + .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.')) .option('--key ', $('The JSON key.')) @@ -1999,62 +1920,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set win-rm - var catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM0 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsWinRM0 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM0.category('win-rm') - .description($('Commands to set/remove/add win-rm of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsWinRM0.command('set') - .description($('Set win-rm in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--listeners ', $('Set the listeners value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/osProfile/windowsConfiguration/winRM'; - var paramPath = options.path + '/' + 'listeners'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.listeners) { - if (options.parse && options.listeners) { - options.listeners = JSON.parse(options.listeners); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.listeners}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove win-rm + //config remove win-rm var catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('win-rm') - .description($('Commands to set/remove/add win-rm of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.command('remove') - .description($('Remove win-rm in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsWinRM1.command('win-rm') + .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.')) .option('--listeners', $('Remove the listeners value.')) @@ -2091,14 +1964,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add win-rm + //config add win-rm var catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('win-rm') - .description($('Commands to set/remove/add win-rm of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.command('add') - .description($('Add win-rm in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = catparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2 = parametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsWinRM2.command('win-rm') + .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.')) .option('--key ', $('The JSON key.')) @@ -2143,14 +2016,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set listeners + //config set listeners var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('listeners') - .description($('Commands to set/remove/add listeners of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.command('set') - .description($('Set listeners in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsListeners0.command('listeners') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2207,14 +2080,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove listeners + //config remove listeners var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('listeners') - .description($('Commands to set/remove/add listeners of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.command('remove') - .description($('Remove listeners in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsListeners1.command('listeners') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2257,14 +2130,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add listeners + //config add listeners var catparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('listeners') - .description($('Commands to set/remove/add listeners of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.command('add') - .description($('Add listeners in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = catparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2 = parametersCreateOrUpdateVirtualMachineScaleSetsListeners2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsListeners2.command('listeners') + .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.')) .option('--key ', $('The JSON key.')) @@ -2320,14 +2193,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set linux-configuration + //config set linux-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('linux-configuration') - .description($('Commands to set/remove/add linux-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.command('set') - .description($('Set linux-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration0.command('linux-configuration') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -2380,14 +2253,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove linux-configuration + //config remove linux-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('linux-configuration') - .description($('Commands to set/remove/add linux-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.command('remove') - .description($('Remove linux-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration1.command('linux-configuration') + .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.')) .option('--disable-password-authentication', $('Remove the disable-password-authentication value.')) @@ -2429,14 +2302,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add linux-configuration + //config add linux-configuration var catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('linux-configuration') - .description($('Commands to set/remove/add linux-configuration of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.command('add') - .description($('Add linux-configuration in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2 = parametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsLinuxConfiguration2.command('linux-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -2493,62 +2366,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set ssh - var catparametersCreateOrUpdateVirtualMachineScaleSetsSsh0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSsh0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSsh0 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh0.category('ssh') - .description($('Commands to set/remove/add ssh of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSsh0.command('set') - .description($('Set ssh in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--public-keys ', $('Set the public-keys value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/osProfile/linuxConfiguration/ssh'; - var paramPath = options.path + '/' + 'publicKeys'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.publicKeys) { - if (options.parse && options.publicKeys) { - options.publicKeys = JSON.parse(options.publicKeys); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.publicKeys}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove ssh + //config remove ssh var catparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('ssh') - .description($('Commands to set/remove/add ssh of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.command('remove') - .description($('Remove ssh in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsSsh1.command('ssh') + .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.')) .option('--public-keys', $('Remove the public-keys value.')) @@ -2585,14 +2410,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add ssh + //config add ssh var catparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('ssh') - .description($('Commands to set/remove/add ssh of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.command('add') - .description($('Add ssh in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2 = parametersCreateOrUpdateVirtualMachineScaleSetsSsh2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsSsh2.command('ssh') + .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.')) .option('--key ', $('The JSON key.')) @@ -2637,14 +2462,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set public-keys + //config set public-keys var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('public-keys') - .description($('Commands to set/remove/add public-keys of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.command('set') - .description($('Set public-keys in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys0.command('public-keys') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2701,14 +2526,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove public-keys + //config remove public-keys var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('public-keys') - .description($('Commands to set/remove/add public-keys of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.command('remove') - .description($('Remove public-keys in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys1.command('public-keys') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2751,14 +2576,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add public-keys + //config add public-keys var catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('public-keys') - .description($('Commands to set/remove/add public-keys of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.command('add') - .description($('Add public-keys in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = catparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2 = parametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsPublicKeys2.command('public-keys') + .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.')) .option('--key ', $('The JSON key.')) @@ -2814,78 +2639,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set secrets - var catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSecrets0 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets0.category('secrets') - .description($('Commands to set/remove/add secrets of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSecrets0.command('set') - .description($('Set secrets in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--index ', $('Indexer: index.')) - .option('--value ', $('The input string value for the indexed item.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--source-vault ', $('Set the source-vault value.')) - .option('--vault-certificates ', $('Set the vault-certificates value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/osProfile/secrets' + (options.index ? ('/' + options.index) : ''); - if (options.value) { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - } - var paramPath = options.path + '/' + 'sourceVault'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.sourceVault) { - if (options.parse && options.sourceVault) { - options.sourceVault = JSON.parse(options.sourceVault); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.sourceVault}]); - } - paramPath = options.path + '/' + 'vaultCertificates'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.vaultCertificates) { - if (options.parse && options.vaultCertificates) { - options.vaultCertificates = JSON.parse(options.vaultCertificates); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.vaultCertificates}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove secrets + //config remove secrets var catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('secrets') - .description($('Commands to set/remove/add secrets of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.command('remove') - .description($('Remove secrets in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsSecrets1.command('secrets') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2928,14 +2689,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add secrets + //config add secrets var catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('secrets') - .description($('Commands to set/remove/add secrets of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.command('add') - .description($('Add secrets in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2 = parametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsSecrets2.command('secrets') + .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.')) .option('--key ', $('The JSON key.')) @@ -2991,14 +2752,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set source-vault + //config set source-vault var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('source-vault') - .description($('Commands to set/remove/add source-vault of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.command('set') - .description($('Set source-vault in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault0.command('source-vault') + .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.')) .option('--secrets-index ', $('Indexer: secrets-index.')) @@ -3040,14 +2801,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove source-vault + //config remove source-vault var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('source-vault') - .description($('Commands to set/remove/add source-vault of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.command('remove') - .description($('Remove source-vault in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault1.command('source-vault') + .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.')) .option('--secrets-index ', $('Indexer: secrets-index.')) @@ -3085,14 +2846,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add source-vault + //config add source-vault var catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('source-vault') - .description($('Commands to set/remove/add source-vault of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.command('add') - .description($('Add source-vault in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2 = parametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsSourceVault2.command('source-vault') + .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.')) .option('--key ', $('The JSON key.')) @@ -3137,14 +2898,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set vault-certificates + //config set vault-certificates var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('vault-certificates') - .description($('Commands to set/remove/add vault-certificates of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.command('set') - .description($('Set vault-certificates in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates0.command('vault-certificates') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3202,14 +2963,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove vault-certificates + //config remove vault-certificates var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('vault-certificates') - .description($('Commands to set/remove/add vault-certificates of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.command('remove') - .description($('Remove vault-certificates in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates1.command('vault-certificates') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3253,14 +3014,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add vault-certificates + //config add vault-certificates var catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('vault-certificates') - .description($('Commands to set/remove/add vault-certificates of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.command('add') - .description($('Add vault-certificates in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2 = parametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsVaultCertificates2.command('vault-certificates') + .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.')) .option('--key ', $('The JSON key.')) @@ -3316,73 +3077,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set storage-profile - var catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0.category('storage-profile') - .description($('Commands to set/remove/add storage-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile0.command('set') - .description($('Set storage-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--image-reference ', $('Set the image-reference value.')) - .option('--os-disk ', $('Set the os-disk value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/storageProfile'; - var paramPath = options.path + '/' + 'imageReference'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.imageReference) { - if (options.parse && options.imageReference) { - options.imageReference = JSON.parse(options.imageReference); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.imageReference}]); - } - paramPath = options.path + '/' + 'osDisk'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.osDisk) { - if (options.parse && options.osDisk) { - options.osDisk = JSON.parse(options.osDisk); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.osDisk}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove storage-profile + //config remove storage-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('storage-profile') - .description($('Commands to set/remove/add storage-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.command('remove') - .description($('Remove storage-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile1.command('storage-profile') + .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.')) .option('--image-reference', $('Remove the image-reference value.')) @@ -3424,14 +3126,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add storage-profile + //config add storage-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('storage-profile') - .description($('Commands to set/remove/add storage-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.command('add') - .description($('Add storage-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsStorageProfile2.command('storage-profile') + .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.')) .option('--key ', $('The JSON key.')) @@ -3487,14 +3189,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set image-reference + //config set image-reference var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('image-reference') - .description($('Commands to set/remove/add image-reference of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.command('set') - .description($('Set image-reference in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsImageReference0.command('image-reference') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -3568,14 +3270,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove image-reference + //config remove image-reference var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('image-reference') - .description($('Commands to set/remove/add image-reference of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.command('remove') - .description($('Remove image-reference in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsImageReference1.command('image-reference') + .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.')) .option('--publisher', $('Remove the publisher value.')) @@ -3627,14 +3329,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add image-reference + //config add image-reference var catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('image-reference') - .description($('Commands to set/remove/add image-reference of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.command('add') - .description($('Add image-reference in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2 = parametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsImageReference2.command('image-reference') + .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.')) .option('--key ', $('The JSON key.')) @@ -3712,14 +3414,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set os-disk + //config set os-disk var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('os-disk') - .description($('Commands to set/remove/add os-disk of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.command('set') - .description($('Set os-disk in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk0.command('os-disk') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -3815,14 +3517,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove os-disk + //config remove os-disk var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('os-disk') - .description($('Commands to set/remove/add os-disk of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.command('remove') - .description($('Remove os-disk in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk1.command('os-disk') + .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.')) .option('--name', $('Remove the name value.')) @@ -3884,14 +3586,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add os-disk + //config add os-disk var catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('os-disk') - .description($('Commands to set/remove/add os-disk of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.command('add') - .description($('Add os-disk in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = catparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2 = parametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsOsDisk2.command('os-disk') + .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.')) .option('--key ', $('The JSON key.')) @@ -3991,14 +3693,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set image + //config set image var catparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImage0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = parametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('image') - .description($('Commands to set/remove/add image of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsImage0.command('set') - .description($('Set image in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImage0 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsImage0 = parametersCreateOrUpdateVirtualMachineScaleSetsImage0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsImage0.command('image') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -4039,14 +3741,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove image + //config remove image var catparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImage1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = parametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('image') - .description($('Commands to set/remove/add image of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1.command('remove') - .description($('Remove image in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImage1 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1 = parametersCreateOrUpdateVirtualMachineScaleSetsImage1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsImage1.command('image') + .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.')) .option('--uri', $('Remove the uri value.')) @@ -4083,14 +3785,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add image + //config add image var catparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsImage2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = parametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('image') - .description($('Commands to set/remove/add image of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsImage2.command('add') - .description($('Add image in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsImage2 = catparametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsImage2 = parametersCreateOrUpdateVirtualMachineScaleSetsImage2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsImage2.command('image') + .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.')) .option('--key ', $('The JSON key.')) @@ -4135,14 +3837,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set vhd-containers + //config set vhd-containers var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('vhd-containers') - .description($('Commands to set/remove/add vhd-containers of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.command('set') - .description($('Set vhd-containers in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers0.command('vhd-containers') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4177,14 +3879,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove vhd-containers + //config remove vhd-containers var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('vhd-containers') - .description($('Commands to set/remove/add vhd-containers of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.command('remove') - .description($('Remove vhd-containers in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers1.command('vhd-containers') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4211,14 +3913,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add vhd-containers + //config add vhd-containers var catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('vhd-containers') - .description($('Commands to set/remove/add vhd-containers of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.command('add') - .description($('Add vhd-containers in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = catparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2 = parametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsVhdContainers2.command('vhd-containers') + .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.')) .option('--key ', $('The JSON key.')) @@ -4252,62 +3954,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set network-profile - var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0.category('network-profile') - .description($('Commands to set/remove/add network-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile0.command('set') - .description($('Set network-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--network-interface-configurations ', $('Set the network-interface-configurations value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/networkProfile'; - var paramPath = options.path + '/' + 'networkInterfaceConfigurations'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.networkInterfaceConfigurations) { - if (options.parse && options.networkInterfaceConfigurations) { - options.networkInterfaceConfigurations = JSON.parse(options.networkInterfaceConfigurations); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.networkInterfaceConfigurations}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove network-profile + //config remove network-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('network-profile') - .description($('Commands to set/remove/add network-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.command('remove') - .description($('Remove network-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile1.command('network-profile') + .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.')) .option('--network-interface-configurations', $('Remove the network-interface-configurations value.')) @@ -4344,14 +3998,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add network-profile + //config add network-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('network-profile') - .description($('Commands to set/remove/add network-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.command('add') - .description($('Add network-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkProfile2.command('network-profile') + .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.')) .option('--key ', $('The JSON key.')) @@ -4396,14 +4050,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set network-interface-configurations + //config set network-interface-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('network-interface-configurations') - .description($('Commands to set/remove/add network-interface-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.command('set') - .description($('Set network-interface-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations0.command('network-interface-configurations') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4483,14 +4137,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove network-interface-configurations + //config remove network-interface-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('network-interface-configurations') - .description($('Commands to set/remove/add network-interface-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.command('remove') - .description($('Remove network-interface-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations1.command('network-interface-configurations') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4543,14 +4197,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add network-interface-configurations + //config add network-interface-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('network-interface-configurations') - .description($('Commands to set/remove/add network-interface-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.command('add') - .description($('Add network-interface-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsNetworkInterfaceConfigurations2.command('network-interface-configurations') + .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.')) .option('--key ', $('The JSON key.')) @@ -4629,14 +4283,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set ip-configurations + //config set ip-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('ip-configurations') - .description($('Commands to set/remove/add ip-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.command('set') - .description($('Set ip-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations0.command('ip-configurations') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4727,14 +4381,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove ip-configurations + //config remove ip-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('ip-configurations') - .description($('Commands to set/remove/add ip-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.command('remove') - .description($('Remove ip-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations1.command('ip-configurations') + .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.')) .option('--index ', $('Indexer: index.')) @@ -4793,14 +4447,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add ip-configurations + //config add ip-configurations var catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('ip-configurations') - .description($('Commands to set/remove/add ip-configurations of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.command('add') - .description($('Add ip-configurations in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = catparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2 = parametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsIpConfigurations2.command('ip-configurations') + .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.')) .option('--key ', $('The JSON key.')) @@ -4889,14 +4543,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set subnet + //config set subnet var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('subnet') - .description($('Commands to set/remove/add subnet of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.command('set') - .description($('Set subnet in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsSubnet0.command('subnet') + .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.')) .option('--ip-configurations-index ', $('Indexer: ip-configurations-index.')) @@ -4939,14 +4593,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove subnet + //config remove subnet var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('subnet') - .description($('Commands to set/remove/add subnet of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.command('remove') - .description($('Remove subnet in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsSubnet1.command('subnet') + .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.')) .option('--ip-configurations-index ', $('Indexer: ip-configurations-index.')) @@ -4985,14 +4639,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add subnet + //config add subnet var catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('subnet') - .description($('Commands to set/remove/add subnet of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.command('add') - .description($('Add subnet in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = catparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2 = parametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsSubnet2.command('subnet') + .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.')) .option('--key ', $('The JSON key.')) @@ -5037,14 +4691,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set load-balancer-backend-address-pools + //config set load-balancer-backend-address-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('load-balancer-backend-address-pools') - .description($('Commands to set/remove/add load-balancer-backend-address-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.command('set') - .description($('Set load-balancer-backend-address-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools0.command('load-balancer-backend-address-pools') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5092,14 +4746,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove load-balancer-backend-address-pools + //config remove load-balancer-backend-address-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('load-balancer-backend-address-pools') - .description($('Commands to set/remove/add load-balancer-backend-address-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.command('remove') - .description($('Remove load-balancer-backend-address-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools1.command('load-balancer-backend-address-pools') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5139,14 +4793,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add load-balancer-backend-address-pools + //config add load-balancer-backend-address-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('load-balancer-backend-address-pools') - .description($('Commands to set/remove/add load-balancer-backend-address-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.command('add') - .description($('Add load-balancer-backend-address-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerBackendAddressPools2.command('load-balancer-backend-address-pools') + .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.')) .option('--key ', $('The JSON key.')) @@ -5191,14 +4845,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set load-balancer-inbound-nat-pools + //config set load-balancer-inbound-nat-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('load-balancer-inbound-nat-pools') - .description($('Commands to set/remove/add load-balancer-inbound-nat-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.command('set') - .description($('Set load-balancer-inbound-nat-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools0.command('load-balancer-inbound-nat-pools') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5246,14 +4900,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove load-balancer-inbound-nat-pools + //config remove load-balancer-inbound-nat-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('load-balancer-inbound-nat-pools') - .description($('Commands to set/remove/add load-balancer-inbound-nat-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.command('remove') - .description($('Remove load-balancer-inbound-nat-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools1.command('load-balancer-inbound-nat-pools') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5293,14 +4947,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add load-balancer-inbound-nat-pools + //config add load-balancer-inbound-nat-pools var catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('load-balancer-inbound-nat-pools') - .description($('Commands to set/remove/add load-balancer-inbound-nat-pools of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.command('add') - .description($('Add load-balancer-inbound-nat-pools in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = catparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2 = parametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsLoadBalancerInboundNatPools2.command('load-balancer-inbound-nat-pools') + .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.')) .option('--key ', $('The JSON key.')) @@ -5345,62 +4999,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set extension-profile - var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0.category('extension-profile') - .description($('Commands to set/remove/add extension-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile0.command('set') - .description($('Set extension-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--extensions ', $('Set the extensions value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/virtualMachineProfile/extensionProfile'; - var paramPath = options.path + '/' + 'extensions'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.extensions) { - if (options.parse && options.extensions) { - options.extensions = JSON.parse(options.extensions); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.extensions}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //create-or-update-parameters remove extension-profile + //config remove extension-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('extension-profile') - .description($('Commands to set/remove/add extension-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.command('remove') - .description($('Remove extension-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile1.command('extension-profile') + .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.')) .option('--extensions', $('Remove the extensions value.')) @@ -5437,14 +5043,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add extension-profile + //config add extension-profile var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('extension-profile') - .description($('Commands to set/remove/add extension-profile of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.command('add') - .description($('Add extension-profile in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsExtensionProfile2.command('extension-profile') + .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.')) .option('--key ', $('The JSON key.')) @@ -5489,14 +5095,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters set extensions + //config set extensions var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of virtual-machine-scale-sets in create-or-update-parameters file.')); - setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.command('set') - .description($('Set extensions in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.category('set') + .description($('Commands to set components of virtual-machine-scale-sets in config file.')); + setparametersCreateOrUpdateVirtualMachineScaleSetsExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5631,14 +5237,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-or-update-parameters remove extensions + //config remove extensions var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('create-or-update-parameters') - .description($('Commands to manage parameter for your virtual-machine-scale-sets.')); - var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of virtual-machine-scale-sets in create-or-update-parameters file.')); - removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.command('remove') - .description($('Remove extensions in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.category('remove') + .description($('Commands to remove components of virtual-machine-scale-sets in config file.')); + removeparametersCreateOrUpdateVirtualMachineScaleSetsExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -5716,14 +5322,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //create-or-update-parameters add extensions + //config add extensions var catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = cli.category('vmss'); - var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('create-or-update-parameters') - .description($('Commands to manage the parameter input file for your virtual-machine-scale-sets.')); - var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of virtual-machine-scale-sets in create-or-update-parameters file.')); - addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.command('add') - .description($('Add extensions in create-or-update-parameters 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + var parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = catparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('config') + .description($('Commands to manage configuration of virtual-machine-scale-sets in the parameter file.')); + var addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2 = parametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.category('add') + .description($('Commands to add components of virtual-machine-scale-sets in config file.')); + addparametersCreateOrUpdateVirtualMachineScaleSetsExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -5893,8 +5499,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -5904,7 +5510,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.deallocate(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets Delete @@ -5934,7 +5542,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.deleteMethod(resourceGroupName, vMScaleSetName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets DeleteInstances @@ -5971,8 +5581,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -5982,7 +5592,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.deleteInstances(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets Get @@ -6012,7 +5624,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.get(resourceGroupName, vMScaleSetName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets GetInstanceView @@ -6042,7 +5656,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.getInstanceView(resourceGroupName, vMScaleSetName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets List @@ -6160,7 +5776,9 @@ exports.init = function (cli) { nextPageLink = pageResult.nextPageLink; } - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets PowerOff @@ -6197,8 +5815,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -6208,7 +5826,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.powerOff(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets Reimage @@ -6238,7 +5858,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.reimage(resourceGroupName, vMScaleSetName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets Restart @@ -6275,8 +5897,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -6286,7 +5908,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.restart(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets Start @@ -6323,8 +5947,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -6334,7 +5958,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.start(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSets UpdateInstances @@ -6371,8 +5997,8 @@ exports.init = function (cli) { instanceIdsObj = JSON.parse(fileContent); } else { - var instanceIdsValArr = instanceIds.split(','); - cli.output.verbose('instanceIdsValArr : ' + instanceIdsValArr); + var instanceIdsValArr = instanceIds ? instanceIds.split(',') : []; + cli.output.verbose('instanceIds : ' + instanceIdsValArr); instanceIdsObj = []; for (var item in instanceIdsValArr) { instanceIdsObj.push(instanceIdsValArr[item]); @@ -6382,7 +6008,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSets.updateInstances(resourceGroupName, vMScaleSetName, instanceIdsObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Deallocate @@ -6419,7 +6047,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.deallocate(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Delete @@ -6456,7 +6086,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.deleteMethod(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Get @@ -6493,7 +6125,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.get(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs GetInstanceView @@ -6530,7 +6164,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.getInstanceView(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs List @@ -6617,7 +6253,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.powerOff(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Reimage @@ -6654,7 +6292,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.reimage(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Restart @@ -6691,7 +6331,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.restart(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* VirtualMachineScaleSetVMs Start @@ -6728,7 +6370,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeManagementClient(subscription); var result = computeManagementClient.virtualMachineScaleSetVMs.start(resourceGroupName, vMScaleSetName, instanceId, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); diff --git a/src/ResourceManager/Compute/Commands.Compute/Microsoft.Azure.Commands.Compute.dll-Help.psd1 b/src/ResourceManager/Compute/Commands.Compute/Microsoft.Azure.Commands.Compute.dll-Help.psd1 index 4343bd6c4031..7688b227c4b2 100644 --- a/src/ResourceManager/Compute/Commands.Compute/Microsoft.Azure.Commands.Compute.dll-Help.psd1 +++ b/src/ResourceManager/Compute/Commands.Compute/Microsoft.Azure.Commands.Compute.dll-Help.psd1 @@ -88,6 +88,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/DataFactories/AzureRM.DataFactories.psd1 b/src/ResourceManager/DataFactories/AzureRM.DataFactories.psd1 index 1e703aa42179..b7fb5cac4843 100644 --- a/src/ResourceManager/DataFactories/AzureRM.DataFactories.psd1 +++ b/src/ResourceManager/DataFactories/AzureRM.DataFactories.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/DataFactories/Commands.DataFactories.Test/Commands.DataFactories.Test.csproj b/src/ResourceManager/DataFactories/Commands.DataFactories.Test/Commands.DataFactories.Test.csproj index 4da333ebb84d..37565d16d5c8 100644 --- a/src/ResourceManager/DataFactories/Commands.DataFactories.Test/Commands.DataFactories.Test.csproj +++ b/src/ResourceManager/DataFactories/Commands.DataFactories.Test/Commands.DataFactories.Test.csproj @@ -131,9 +131,9 @@ ..\..\..\packages\WindowsAzure.Storage.5.0.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/DataFactories/Commands.DataFactories.Test/packages.config b/src/ResourceManager/DataFactories/Commands.DataFactories.Test/packages.config index 5faf69fbf99b..38d8a0a85a94 100644 --- a/src/ResourceManager/DataFactories/Commands.DataFactories.Test/packages.config +++ b/src/ResourceManager/DataFactories/Commands.DataFactories.Test/packages.config @@ -23,7 +23,7 @@ - + diff --git a/src/ResourceManager/DataLakeAnalytics/AzureRM.DataLakeAnalytics.psd1 b/src/ResourceManager/DataLakeAnalytics/AzureRM.DataLakeAnalytics.psd1 index ec34998f2f68..c12bcdd525d3 100644 --- a/src/ResourceManager/DataLakeAnalytics/AzureRM.DataLakeAnalytics.psd1 +++ b/src/ResourceManager/DataLakeAnalytics/AzureRM.DataLakeAnalytics.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/Commands.DataLakeAnalytics.Test.csproj b/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/Commands.DataLakeAnalytics.Test.csproj index 077bf5570a42..5471db1ff3dd 100644 --- a/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/Commands.DataLakeAnalytics.Test.csproj +++ b/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/Commands.DataLakeAnalytics.Test.csproj @@ -130,9 +130,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/packages.config b/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/packages.config index 1fa7fdc5239b..78d2481d1af4 100644 --- a/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/packages.config +++ b/src/ResourceManager/DataLakeAnalytics/Commands.DataLakeAnalytics.Test/packages.config @@ -21,7 +21,7 @@ - + diff --git a/src/ResourceManager/DataLakeStore/AzureRM.DataLakeStore.psd1 b/src/ResourceManager/DataLakeStore/AzureRM.DataLakeStore.psd1 index a05628612808..6114c6c1a1d6 100644 --- a/src/ResourceManager/DataLakeStore/AzureRM.DataLakeStore.psd1 +++ b/src/ResourceManager/DataLakeStore/AzureRM.DataLakeStore.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/Commands.DataLakeStore.Test.csproj b/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/Commands.DataLakeStore.Test.csproj index 5b00c40f8847..c511996a2355 100644 --- a/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/Commands.DataLakeStore.Test.csproj +++ b/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/Commands.DataLakeStore.Test.csproj @@ -125,9 +125,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/packages.config b/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/packages.config index 8f74492da226..2041d7d5efaf 100644 --- a/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/packages.config +++ b/src/ResourceManager/DataLakeStore/Commands.DataLakeStore.Test/packages.config @@ -20,7 +20,7 @@ - + diff --git a/src/ResourceManager/Dns/AzureRM.Dns.psd1 b/src/ResourceManager/Dns/AzureRM.Dns.psd1 index 7b766b3e9bf7..6d91df361049 100644 --- a/src/ResourceManager/Dns/AzureRM.Dns.psd1 +++ b/src/ResourceManager/Dns/AzureRM.Dns.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Dns/Commands.Dns.Test/Commands.Dns.Test.csproj b/src/ResourceManager/Dns/Commands.Dns.Test/Commands.Dns.Test.csproj index dd609ef5ed14..f7fdb1d4823f 100644 --- a/src/ResourceManager/Dns/Commands.Dns.Test/Commands.Dns.Test.csproj +++ b/src/ResourceManager/Dns/Commands.Dns.Test/Commands.Dns.Test.csproj @@ -98,9 +98,9 @@ False ..\..\..\packages\Microsoft.Bcl.Async.1.0.168\lib\net40\Microsoft.Threading.Tasks.Extensions.Desktop.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Dns/Commands.Dns.Test/packages.config b/src/ResourceManager/Dns/Commands.Dns.Test/packages.config index 701a14c7ec0a..96591fdf18dd 100644 --- a/src/ResourceManager/Dns/Commands.Dns.Test/packages.config +++ b/src/ResourceManager/Dns/Commands.Dns.Test/packages.config @@ -14,7 +14,7 @@ - + diff --git a/src/ResourceManager/Dns/Commands.Dns/Microsoft.Azure.Commands.Dns.dll-help.psd1 b/src/ResourceManager/Dns/Commands.Dns/Microsoft.Azure.Commands.Dns.dll-help.psd1 index aff7c38b0600..b762d749ce16 100644 --- a/src/ResourceManager/Dns/Commands.Dns/Microsoft.Azure.Commands.Dns.dll-help.psd1 +++ b/src/ResourceManager/Dns/Commands.Dns/Microsoft.Azure.Commands.Dns.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/HDInsight/AzureRM.HDInsight.psd1 b/src/ResourceManager/HDInsight/AzureRM.HDInsight.psd1 index 03d6c9dfdf93..c98ff2ff95b4 100644 --- a/src/ResourceManager/HDInsight/AzureRM.HDInsight.psd1 +++ b/src/ResourceManager/HDInsight/AzureRM.HDInsight.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj b/src/ResourceManager/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj index 243ab2aa9312..05fb22cf208b 100644 --- a/src/ResourceManager/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj +++ b/src/ResourceManager/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj @@ -124,9 +124,9 @@ ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll diff --git a/src/ResourceManager/HDInsight/Commands.HDInsight.Test/packages.config b/src/ResourceManager/HDInsight/Commands.HDInsight.Test/packages.config index 946cf72e0886..468535ba808d 100644 --- a/src/ResourceManager/HDInsight/Commands.HDInsight.Test/packages.config +++ b/src/ResourceManager/HDInsight/Commands.HDInsight.Test/packages.config @@ -23,7 +23,7 @@ - + diff --git a/src/ResourceManager/HDInsight/Commands.HDInsight/Microsoft.Azure.Commands.HDInsight.dll-help.psd1 b/src/ResourceManager/HDInsight/Commands.HDInsight/Microsoft.Azure.Commands.HDInsight.dll-help.psd1 index 654fc3e66888..ecbddeb6227d 100644 --- a/src/ResourceManager/HDInsight/Commands.HDInsight/Microsoft.Azure.Commands.HDInsight.dll-help.psd1 +++ b/src/ResourceManager/HDInsight/Commands.HDInsight/Microsoft.Azure.Commands.HDInsight.dll-help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Insights/AzureRM.Insights.psd1 b/src/ResourceManager/Insights/AzureRM.Insights.psd1 index 7a945ef08e61..85a521d1b431 100644 --- a/src/ResourceManager/Insights/AzureRM.Insights.psd1 +++ b/src/ResourceManager/Insights/AzureRM.Insights.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Insights/Commands.Insights.Test/Commands.Insights.Test.csproj b/src/ResourceManager/Insights/Commands.Insights.Test/Commands.Insights.Test.csproj index 2aba9868db10..9f47d1a75330 100644 --- a/src/ResourceManager/Insights/Commands.Insights.Test/Commands.Insights.Test.csproj +++ b/src/ResourceManager/Insights/Commands.Insights.Test/Commands.Insights.Test.csproj @@ -113,9 +113,9 @@ ..\..\..\packages\Microsoft.Azure.KeyVault.Core.1.0.0\lib\net40\Microsoft.Azure.KeyVault.Core.dll True - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Insights/Commands.Insights.Test/packages.config b/src/ResourceManager/Insights/Commands.Insights.Test/packages.config index d2653ce3cdbb..cc18a79ef3b4 100644 --- a/src/ResourceManager/Insights/Commands.Insights.Test/packages.config +++ b/src/ResourceManager/Insights/Commands.Insights.Test/packages.config @@ -19,7 +19,7 @@ - + diff --git a/src/ResourceManager/Intune/AzureRM.Intune.psd1 b/src/ResourceManager/Intune/AzureRM.Intune.psd1 index 230a5d9669ba..e186dfa9fa94 100644 --- a/src/ResourceManager/Intune/AzureRM.Intune.psd1 +++ b/src/ResourceManager/Intune/AzureRM.Intune.psd1 @@ -97,16 +97,16 @@ PrivateData = @{ # Tags = @() # A URL to the license for this module. - # LicenseUri = '' + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' # A URL to the main website for this project. - # ProjectUri = '' + ProjectUri = 'https://github.com/Azure/azure-powershell' # A URL to an icon representing this module. # IconUri = '' # ReleaseNotes of this module - # ReleaseNotes = '' + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' } # End of PSData hashtable diff --git a/src/ResourceManager/Intune/Commands.Intune.Test/Commands.Intune.Test.csproj b/src/ResourceManager/Intune/Commands.Intune.Test/Commands.Intune.Test.csproj index 5a638d8f5d99..52891b1f5bf6 100644 --- a/src/ResourceManager/Intune/Commands.Intune.Test/Commands.Intune.Test.csproj +++ b/src/ResourceManager/Intune/Commands.Intune.Test/Commands.Intune.Test.csproj @@ -110,7 +110,7 @@ True - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Intune/Commands.Intune.Test/packages.config b/src/ResourceManager/Intune/Commands.Intune.Test/packages.config index e117b1edc58e..629805394b9e 100644 --- a/src/ResourceManager/Intune/Commands.Intune.Test/packages.config +++ b/src/ResourceManager/Intune/Commands.Intune.Test/packages.config @@ -15,7 +15,7 @@ - + diff --git a/src/ResourceManager/Intune/Commands.Intune/Microsoft.Azure.Commands.Intune.dll-Help.psd1 b/src/ResourceManager/Intune/Commands.Intune/Microsoft.Azure.Commands.Intune.dll-Help.psd1 index 5cfcb06f38fd..3db1c2ae2255 100644 --- a/src/ResourceManager/Intune/Commands.Intune/Microsoft.Azure.Commands.Intune.dll-Help.psd1 +++ b/src/ResourceManager/Intune/Commands.Intune/Microsoft.Azure.Commands.Intune.dll-Help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/KeyVault/AzureRM.KeyVault.psd1 b/src/ResourceManager/KeyVault/AzureRM.KeyVault.psd1 index 4c2a06051ee9..9956d573fdb6 100644 --- a/src/ResourceManager/KeyVault/AzureRM.KeyVault.psd1 +++ b/src/ResourceManager/KeyVault/AzureRM.KeyVault.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/KeyVault/Commands.KeyVault.Test/Commands.KeyVault.Test.csproj b/src/ResourceManager/KeyVault/Commands.KeyVault.Test/Commands.KeyVault.Test.csproj index 6241b3a05882..6aa2c7408d38 100644 --- a/src/ResourceManager/KeyVault/Commands.KeyVault.Test/Commands.KeyVault.Test.csproj +++ b/src/ResourceManager/KeyVault/Commands.KeyVault.Test/Commands.KeyVault.Test.csproj @@ -120,9 +120,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/KeyVault/Commands.KeyVault.Test/packages.config b/src/ResourceManager/KeyVault/Commands.KeyVault.Test/packages.config index 9a3435e8132b..ebc6a0c14820 100644 --- a/src/ResourceManager/KeyVault/Commands.KeyVault.Test/packages.config +++ b/src/ResourceManager/KeyVault/Commands.KeyVault.Test/packages.config @@ -18,7 +18,7 @@ - + diff --git a/src/ResourceManager/LogicApp/AzureRM.LogicApp.psd1 b/src/ResourceManager/LogicApp/AzureRM.LogicApp.psd1 index 05ac657f9d4d..cfcd0e428410 100644 --- a/src/ResourceManager/LogicApp/AzureRM.LogicApp.psd1 +++ b/src/ResourceManager/LogicApp/AzureRM.LogicApp.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/LogicApp/Commands.LogicApp/Microsoft.Azure.Commands.LogicApp.dll-help.psd1 b/src/ResourceManager/LogicApp/Commands.LogicApp/Microsoft.Azure.Commands.LogicApp.dll-help.psd1 index e8ae99c36f0f..628df62922aa 100644 --- a/src/ResourceManager/LogicApp/Commands.LogicApp/Microsoft.Azure.Commands.LogicApp.dll-help.psd1 +++ b/src/ResourceManager/LogicApp/Commands.LogicApp/Microsoft.Azure.Commands.LogicApp.dll-help.psd1 @@ -80,6 +80,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Network/AzureRM.Network.psd1 b/src/ResourceManager/Network/AzureRM.Network.psd1 index 9c3ec79afa0c..682e7b720275 100644 --- a/src/ResourceManager/Network/AzureRM.Network.psd1 +++ b/src/ResourceManager/Network/AzureRM.Network.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Network/Commands.Network.Test/Commands.Network.Test.csproj b/src/ResourceManager/Network/Commands.Network.Test/Commands.Network.Test.csproj index c2ba252dcbd8..44316a22da17 100644 --- a/src/ResourceManager/Network/Commands.Network.Test/Commands.Network.Test.csproj +++ b/src/ResourceManager/Network/Commands.Network.Test/Commands.Network.Test.csproj @@ -109,9 +109,9 @@ False ..\..\..\packages\Microsoft.Bcl.Async.1.0.168\lib\net40\Microsoft.Threading.Tasks.Extensions.Desktop.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/Network/Commands.Network.Test/packages.config b/src/ResourceManager/Network/Commands.Network.Test/packages.config index 704a31e28597..94ab413fe2b5 100644 --- a/src/ResourceManager/Network/Commands.Network.Test/packages.config +++ b/src/ResourceManager/Network/Commands.Network.Test/packages.config @@ -18,7 +18,7 @@ - + diff --git a/src/ResourceManager/Network/Commands.Network/Microsoft.Azure.Commands.Network.dll-Help.psd1 b/src/ResourceManager/Network/Commands.Network/Microsoft.Azure.Commands.Network.dll-Help.psd1 index 91649e130c0a..0b881d02af0e 100644 --- a/src/ResourceManager/Network/Commands.Network/Microsoft.Azure.Commands.Network.dll-Help.psd1 +++ b/src/ResourceManager/Network/Commands.Network/Microsoft.Azure.Commands.Network.dll-Help.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/NotificationHubs/AzureRM.NotificationHubs.psd1 b/src/ResourceManager/NotificationHubs/AzureRM.NotificationHubs.psd1 index 0f2545f7d8c2..0db8f59423a5 100644 --- a/src/ResourceManager/NotificationHubs/AzureRM.NotificationHubs.psd1 +++ b/src/ResourceManager/NotificationHubs/AzureRM.NotificationHubs.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/NotificationHubs/Commands.NotificationHubs/Microsoft.Azure.Commands.NotificationHubs.dll-help.psd1 b/src/ResourceManager/NotificationHubs/Commands.NotificationHubs/Microsoft.Azure.Commands.NotificationHubs.dll-help.psd1 index c7cda0090bbb..9c64974a9465 100644 --- a/src/ResourceManager/NotificationHubs/Commands.NotificationHubs/Microsoft.Azure.Commands.NotificationHubs.dll-help.psd1 +++ b/src/ResourceManager/NotificationHubs/Commands.NotificationHubs/Microsoft.Azure.Commands.NotificationHubs.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/OperationalInsights/AzureRM.OperationalInsights.psd1 b/src/ResourceManager/OperationalInsights/AzureRM.OperationalInsights.psd1 index adee92dc9699..d5ac77c01624 100644 --- a/src/ResourceManager/OperationalInsights/AzureRM.OperationalInsights.psd1 +++ b/src/ResourceManager/OperationalInsights/AzureRM.OperationalInsights.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/Commands.OperationalInsights.Test.csproj b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/Commands.OperationalInsights.Test.csproj index b443b4963014..d5b0af765143 100644 --- a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/Commands.OperationalInsights.Test.csproj +++ b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/Commands.OperationalInsights.Test.csproj @@ -103,9 +103,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/packages.config b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/packages.config index c29890a7c258..e97d604c0e5a 100644 --- a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/packages.config +++ b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights.Test/packages.config @@ -17,7 +17,7 @@ - + diff --git a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights/Microsoft.Azure.Commands.OperationalInsights.dll-Help.psd1 b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights/Microsoft.Azure.Commands.OperationalInsights.dll-Help.psd1 index f1adc9f05087..36b75dd12d67 100644 --- a/src/ResourceManager/OperationalInsights/Commands.OperationalInsights/Microsoft.Azure.Commands.OperationalInsights.dll-Help.psd1 +++ b/src/ResourceManager/OperationalInsights/Commands.OperationalInsights/Microsoft.Azure.Commands.OperationalInsights.dll-Help.psd1 @@ -82,6 +82,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Profile/AzureRM.Profile.psd1 b/src/ResourceManager/Profile/AzureRM.Profile.psd1 index 2bc5bce87e48..a3561cc174e0 100644 --- a/src/ResourceManager/Profile/AzureRM.Profile.psd1 +++ b/src/ResourceManager/Profile/AzureRM.Profile.psd1 @@ -88,6 +88,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Profile/Commands.Profile.Test/Commands.Profile.Test.csproj b/src/ResourceManager/Profile/Commands.Profile.Test/Commands.Profile.Test.csproj index 7196ec437299..849dc7b387ec 100644 --- a/src/ResourceManager/Profile/Commands.Profile.Test/Commands.Profile.Test.csproj +++ b/src/ResourceManager/Profile/Commands.Profile.Test/Commands.Profile.Test.csproj @@ -131,8 +131,8 @@ ..\..\..\packages\WindowsAzure.Storage.5.0.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - - ..\..\..\packages\Moq.4.2.1409.1722\lib\net40\Moq.dll + + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll True diff --git a/src/ResourceManager/Profile/Commands.Profile.Test/packages.config b/src/ResourceManager/Profile/Commands.Profile.Test/packages.config index 6b55c58b8594..f7dc443f75ad 100644 --- a/src/ResourceManager/Profile/Commands.Profile.Test/packages.config +++ b/src/ResourceManager/Profile/Commands.Profile.Test/packages.config @@ -21,7 +21,7 @@ - + diff --git a/src/ResourceManager/Profile/Commands.Profile/Microsoft.Azure.Commands.Profile.dll-Help.psd1 b/src/ResourceManager/Profile/Commands.Profile/Microsoft.Azure.Commands.Profile.dll-Help.psd1 index 72aa7e1c063b..8a2f96bd1fd8 100644 --- a/src/ResourceManager/Profile/Commands.Profile/Microsoft.Azure.Commands.Profile.dll-Help.psd1 +++ b/src/ResourceManager/Profile/Commands.Profile/Microsoft.Azure.Commands.Profile.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/RecoveryServices/AzureRM.RecoveryServices.psd1 b/src/ResourceManager/RecoveryServices/AzureRM.RecoveryServices.psd1 index 413aed39eabe..85284fc32e4c 100644 --- a/src/ResourceManager/RecoveryServices/AzureRM.RecoveryServices.psd1 +++ b/src/ResourceManager/RecoveryServices/AzureRM.RecoveryServices.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/RedisCache/AzureRM.RedisCache.psd1 b/src/ResourceManager/RedisCache/AzureRM.RedisCache.psd1 index 5f603864ef53..e2c7d296d957 100644 --- a/src/ResourceManager/RedisCache/AzureRM.RedisCache.psd1 +++ b/src/ResourceManager/RedisCache/AzureRM.RedisCache.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/RedisCache/Commands.RedisCache.Test/Commands.RedisCache.Test.csproj b/src/ResourceManager/RedisCache/Commands.RedisCache.Test/Commands.RedisCache.Test.csproj index 4ff1337f0357..b1986193c23d 100644 --- a/src/ResourceManager/RedisCache/Commands.RedisCache.Test/Commands.RedisCache.Test.csproj +++ b/src/ResourceManager/RedisCache/Commands.RedisCache.Test/Commands.RedisCache.Test.csproj @@ -127,9 +127,9 @@ ..\..\..\packages\WindowsAzure.Storage.6.1.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ResourceManager/RedisCache/Commands.RedisCache.Test/packages.config b/src/ResourceManager/RedisCache/Commands.RedisCache.Test/packages.config index 053c76beb45f..82bdb852c686 100644 --- a/src/ResourceManager/RedisCache/Commands.RedisCache.Test/packages.config +++ b/src/ResourceManager/RedisCache/Commands.RedisCache.Test/packages.config @@ -21,7 +21,7 @@ - + diff --git a/src/ResourceManager/Resources/AzureRM.Resources.psd1 b/src/ResourceManager/Resources/AzureRM.Resources.psd1 index e514aa2e8621..625a7f6dac6c 100644 --- a/src/ResourceManager/Resources/AzureRM.Resources.psd1 +++ b/src/ResourceManager/Resources/AzureRM.Resources.psd1 @@ -86,6 +86,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Resources/Commands.Resources.Test/Commands.Resources.Test.csproj b/src/ResourceManager/Resources/Commands.Resources.Test/Commands.Resources.Test.csproj index 7a470646375b..4ca06b748362 100644 --- a/src/ResourceManager/Resources/Commands.Resources.Test/Commands.Resources.Test.csproj +++ b/src/ResourceManager/Resources/Commands.Resources.Test/Commands.Resources.Test.csproj @@ -132,9 +132,9 @@ ..\..\..\packages\WindowsAzure.Storage.5.0.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/Resources/Commands.Resources.Test/packages.config b/src/ResourceManager/Resources/Commands.Resources.Test/packages.config index 406e4002c706..174a84536ef6 100644 --- a/src/ResourceManager/Resources/Commands.Resources.Test/packages.config +++ b/src/ResourceManager/Resources/Commands.Resources.Test/packages.config @@ -22,7 +22,7 @@ - + diff --git a/src/ResourceManager/Resources/Commands.Resources/AzureResourceManager.psd1 b/src/ResourceManager/Resources/Commands.Resources/AzureResourceManager.psd1 index 4279415e2f0a..724c86d4eadb 100644 --- a/src/ResourceManager/Resources/Commands.Resources/AzureResourceManager.psd1 +++ b/src/ResourceManager/Resources/Commands.Resources/AzureResourceManager.psd1 @@ -139,6 +139,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.psd1 b/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.psd1 index d04c0be16ceb..2acc8833ce7d 100644 --- a/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.psd1 +++ b/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.xml b/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.xml index be0ff169384e..f7fd6245f67a 100644 --- a/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.xml +++ b/src/ResourceManager/Resources/Commands.Resources/Microsoft.Azure.Commands.Resources.dll-Help.xml @@ -14,7 +14,6 @@ - This is the Description section Filters active directory groups. @@ -234,7 +233,6 @@ - This is the Description section Get a group members. @@ -368,7 +366,6 @@ - This is the Description section Filters active directory service principals. @@ -617,7 +614,6 @@ - This is the Description section Filters active directory users. @@ -1473,7 +1469,6 @@ - This is the Description section The Get-AzureRmResourceGroup cmdlet gets the Azure resource groups in your subscription. You can use the Name parameter to select resource groups by name. The default is all resource groups.An Azure resource is a user-managed Azure entity, such as a database server, database, or web site. An Azure resource group is a collection of Azure resources that are deployed as a unit. @@ -1755,7 +1750,6 @@ Tags: - This is the Description section The Get-AzureRmResourceGroupDeployment cmdlet gets the deployments in an Azure resource group. You can use the Name (DeploymentName) and ProvisioningState parameters to filter the deployments. By default, Get-AzureRmResourceGroupDeployment returns all deployments for a specified resource group.An Azure resource is a user-managed Azure entity, such as a database server, database, or web site. An Azure resource group is a collection of Azure resources that are deployed as a unit. A deployment is the operation that makes the resources in the resource group available for use.This cmdlet is very useful for tracking. For debugging, use it with the Get-AzureRmResourceGroupLog cmdlet. @@ -3461,7 +3455,6 @@ ContosoLabsRG WordPress.WordPress Succ - This is the Description section Creates a new azure active directory application. @@ -4013,7 +4006,6 @@ AppPermissions : {{ - This is the Description section Creates a new azure active directory service principal. @@ -4183,7 +4175,6 @@ NewApplication 61b5d8ea-fdc6-40a2 - This is the Description section The New-AzureRmResourceGroup cmdlet creates an Azure resource group and returns an object that represents the resource group. @@ -4385,7 +4376,6 @@ Resources - This is the Description section The New-AzureRmResourceGroupDeployment cmdlet adds a deployment to an existing resource group, including the resources that the deployment requires. To add resources to a resource group without using a template, use the New-AzureRmResource cmdlet. An Azure resource is a user-managed Azure entity, such as a database server, database, website, virtual machine, or storage account. An Azure resource group is a collection of Azure resources that are deployed as a unit, such as the web site, database server, and databases that are required for a financial web site. A deployment uses a resource group template to add resource to a resource group and publish them so they are available in Azure. To add a resource group deployment, specify the name of an existing resource group and a resource group template, which is a JSON string that represents of a resource group for a complex cloud-based service, such as a web portal. The template includes parameter (placeholders) for required resources and configurable property values, likes names and sizes. You can find many templates in the Azure template gallery and you can create your own templates. @@ -6320,7 +6310,6 @@ Resources - This is the Description section Deletes the azure active directory application. @@ -6478,7 +6467,6 @@ Resources - This is the Description section Deletes the azure active directory service principal. @@ -6661,7 +6649,6 @@ Resources - This is the Description section The Remove-AzureRmResourceGroup cmdlet deletes a resource group and its resources from your subscription. By default, Remove-AzureRmResourceGroup prompts you for confirmation. To suppress the prompt, use the Force parameter.To delete a resource, but leave the resource group, use the Remove-AzureRmResource cmdlet. @@ -8100,7 +8087,6 @@ True - This is the Description section The Set-AzureRmResourceGroup cmdlet changes the properties of a resource group. You can use this cmdlet to add, change, or delete the Azure tags applied to a resource group. Use the Name parameter to identify the resource group and the Tag parameter to change the tags. You cannot use this cmdlet to change the name of a resource group. @@ -8574,7 +8560,6 @@ Tags: - This is the Description section The Stop-AzureRmResourceGroupDeployment cmdlet cancels an Azure resource group deployment that is started, but not completed. To stop a deployment, the deployment must have an incomplete provisioning state, such as Provisioning, and not a completed state, such as Provisioned or Failed.An Azure resource is a user-managed entity, such as a website, database, or database server. A resource group is a collection of resources that are deployed as a unit. To deploy a resource group, use the New-AzureRmResourceGroup or New-AzureRmResourceGroupDeployment cmdlets. The New-AzureRmResource cmdlet creates a new resource, but it does not trigger a resource group deployment operation that this cmdlet can stop.This cmdlet stops only one running deployment. Use the Name parameter to stop a particular deployment. If you omit the Name parameter, Stop-AzureRmResourceGroupDeployment searches for a running deployment and stops it, but if it finds more than one running deployment, the command fails.By default, Stop-AzureRmResourceGroupDeployment prompts you for confirmation. To suppress the prompt, use the Force parameter. @@ -8728,7 +8713,6 @@ Tags: - This is the Description section The Test-AzureResourceGroupDeployment cmdlet verifies the validity of a resource group template, its parameters, and parameter values. It returns errors that it finds. Otherwise, it does not return any output. To specify a template, use the TemplateUri or TemplateFile parameters. To specify the template parameter values, use the TemplateParameterFile or TemplateParameterObject parameters, or use the template parameters that are added to the command dynamically when you specify the template. To get the parameters, just type a minus sign (-) to indicate a parameter name and press the TAB key to trigger tab-completion. If you miss a required parameter, the cmdlet prompts you for the value. Parameter values typed at the command line take precedence over values in a template parameter object or file.A resource group template is a JSON-based model of a resource group for a complex cloud-based service, such as a web portal. You can use a resource group template to create a resource group or resource group deployment. The template includes parameter (placeholders) for configurable property values, likes names and sizes. You can find many templates in the Azure template gallery and you can create your own templates. @@ -11951,7 +11935,6 @@ Tags: - This is the Description section The Get-AzureRmResource cmdlet gets the Azure resources in the subscription. By default, it gets all resources in the subscription, but you can use the parameters in the cmdlet to filter the results.An Azure resource is a user-managed Azure entity, such as a database server, database, or website. Every Azure resource is associated with a resource group, which is a collection of resources that are deployed as a unit. @@ -12488,7 +12471,6 @@ Tags: - This is the Description section The New-AzureRmResource cmdlet creates an Azure resource, such as a website, SQL Azure database server, or SQL Azure database, in a new or existing resource group.If a resource with the same name exists in the resource group, the cmdlet prompts for confirmation before replacing the existing resource. To suppress the confirmation prompt, use the Force parameter.A resource is a user-managed Azure entity. A resource group is a collection of resources that are deployed as a unit. Every resource belongs to exactly one resource group.Typically, you use a template to create a resource group (New-AzureRmResourceGroup) and its resources. Then, if necessary, you can use this cmdlet to add additional resources to it. @@ -12729,7 +12711,6 @@ Properties : {[name, ContosoWeb], [state, Running], [hostNames, - This is the Description section The Remove-AzureRmResource cmdlet deletes a resource from your subscription. It does not delete the resource group of the resource. By default, Remove-AzureRmResource prompts you for confirmation. To suppress the prompt, use the Force parameter. @@ -12973,7 +12954,6 @@ True - This is the Description section The Set-AzureRmResource cmdlet changes the properties of an Azure resource. To use the cmdlet, use the Name, ResourceGroupName, ResourceGroupType, and ParentResource parameters to identify the resource, and the PropertyObject parameter to specify the new property names and values.If the command succeeds, it returns the resource with the new properties and values.An Azure resource is a user-managed entity, such as an Azure Website or Azure SQL Database. Some resources have properties, which are user-configured values, like sizes and operational modes. You can specify these values when you create the resource, such as by using the New-AzureRmResource, New-AzureRmResourceGroup, or New-AzureRmResourceGroupDeployment cmdlets. And, you can change the properties by using this cmdlet.To get the properties of a resource, use the Get-AzureRmResource cmdlet to get the resource. Then use the dot method to get the Properties property collection and a particular named property. For example, to get the siteMode property of an object, type (Get-AzureRmResource -Name MyWebSite -ResourceGroupName RG -ResourceType Microsoft.Web/sites -ApiVersion 2014-04-01).Properties.siteMode @@ -13274,7 +13254,6 @@ Tags: - This is the Description section The Get-AzureRmResourceGroupLog cmdlet gets the deployment log entries for a resource group. The entries are very useful for many IT tasks, including maintaining a transaction history, performing statistical analyses, and debugging.By default, Get-AzureRmResourceGroupLog gets the log entries of the currently running or most recently completed deployment for the resource group, but you can use the cmdlet parameters to get the entries for a particular deployment by name or all deployments. diff --git a/src/ResourceManager/SiteRecovery/AzureRM.SiteRecovery.psd1 b/src/ResourceManager/SiteRecovery/AzureRM.SiteRecovery.psd1 index afbf13a75230..392e7f06546f 100644 --- a/src/ResourceManager/SiteRecovery/AzureRM.SiteRecovery.psd1 +++ b/src/ResourceManager/SiteRecovery/AzureRM.SiteRecovery.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Sql/AzureRM.Sql.psd1 b/src/ResourceManager/Sql/AzureRM.Sql.psd1 index 664310608061..1bda1f856ddd 100644 --- a/src/ResourceManager/Sql/AzureRM.Sql.psd1 +++ b/src/ResourceManager/Sql/AzureRM.Sql.psd1 @@ -92,6 +92,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Sql/Commands.Sql.Test/Commands.Sql.Test.csproj b/src/ResourceManager/Sql/Commands.Sql.Test/Commands.Sql.Test.csproj index 9508dedf0f0d..e4ffdce78fbf 100644 --- a/src/ResourceManager/Sql/Commands.Sql.Test/Commands.Sql.Test.csproj +++ b/src/ResourceManager/Sql/Commands.Sql.Test/Commands.Sql.Test.csproj @@ -138,9 +138,9 @@ ..\..\..\packages\WindowsAzure.Storage.5.0.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/Sql/Commands.Sql.Test/packages.config b/src/ResourceManager/Sql/Commands.Sql.Test/packages.config index d27f535e3e3b..f83a297162e5 100644 --- a/src/ResourceManager/Sql/Commands.Sql.Test/packages.config +++ b/src/ResourceManager/Sql/Commands.Sql.Test/packages.config @@ -24,7 +24,7 @@ - + diff --git a/src/ResourceManager/Sql/Commands.Sql/Microsoft.Azure.Commands.Sql.dll-Help.psd1 b/src/ResourceManager/Sql/Commands.Sql/Microsoft.Azure.Commands.Sql.dll-Help.psd1 index f8b93185e710..f4e7fd5b4804 100644 --- a/src/ResourceManager/Sql/Commands.Sql/Microsoft.Azure.Commands.Sql.dll-Help.psd1 +++ b/src/ResourceManager/Sql/Commands.Sql/Microsoft.Azure.Commands.Sql.dll-Help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Storage/AzureRM.Storage.psd1 b/src/ResourceManager/Storage/AzureRM.Storage.psd1 index 2184238a32ba..41934b359bb1 100644 --- a/src/ResourceManager/Storage/AzureRM.Storage.psd1 +++ b/src/ResourceManager/Storage/AzureRM.Storage.psd1 @@ -88,6 +88,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Storage/Commands.Management.Storage/Microsoft.Azure.Commands.Management.Storage.dll-Help.psd1 b/src/ResourceManager/Storage/Commands.Management.Storage/Microsoft.Azure.Commands.Management.Storage.dll-Help.psd1 index 44c2fcf7c808..29c9867da6cf 100644 --- a/src/ResourceManager/Storage/Commands.Management.Storage/Microsoft.Azure.Commands.Management.Storage.dll-Help.psd1 +++ b/src/ResourceManager/Storage/Commands.Management.Storage/Microsoft.Azure.Commands.Management.Storage.dll-Help.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/StreamAnalytics/AzureRM.StreamAnalytics.psd1 b/src/ResourceManager/StreamAnalytics/AzureRM.StreamAnalytics.psd1 index 91115fbed4b6..135abe863098 100644 --- a/src/ResourceManager/StreamAnalytics/AzureRM.StreamAnalytics.psd1 +++ b/src/ResourceManager/StreamAnalytics/AzureRM.StreamAnalytics.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/Commands.StreamAnalytics.Test.csproj b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/Commands.StreamAnalytics.Test.csproj index 562d3619dcbe..3a679e18d555 100644 --- a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/Commands.StreamAnalytics.Test.csproj +++ b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/Commands.StreamAnalytics.Test.csproj @@ -125,9 +125,9 @@ ..\..\..\packages\WindowsAzure.Storage.5.0.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/packages.config b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/packages.config index f310aad16044..e82141916ff4 100644 --- a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/packages.config +++ b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics.Test/packages.config @@ -22,7 +22,7 @@ - + diff --git a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics/Microsoft.Azure.Commands.StreamAnalytics.dll-Help.psd1 b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics/Microsoft.Azure.Commands.StreamAnalytics.dll-Help.psd1 index 6a49da571f52..3062ee661960 100644 --- a/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics/Microsoft.Azure.Commands.StreamAnalytics.dll-Help.psd1 +++ b/src/ResourceManager/StreamAnalytics/Commands.StreamAnalytics/Microsoft.Azure.Commands.StreamAnalytics.dll-Help.psd1 @@ -82,6 +82,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Tags/AzureRM.Tags.psd1 b/src/ResourceManager/Tags/AzureRM.Tags.psd1 index de4861a9ff25..1f7df96b3d16 100644 --- a/src/ResourceManager/Tags/AzureRM.Tags.psd1 +++ b/src/ResourceManager/Tags/AzureRM.Tags.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Tags/Commands.Tags/Microsoft.Azure.Commands.Tags.dll-help.psd1 b/src/ResourceManager/Tags/Commands.Tags/Microsoft.Azure.Commands.Tags.dll-help.psd1 index 71043eb83311..bd95d844845e 100644 --- a/src/ResourceManager/Tags/Commands.Tags/Microsoft.Azure.Commands.Tags.dll-help.psd1 +++ b/src/ResourceManager/Tags/Commands.Tags/Microsoft.Azure.Commands.Tags.dll-help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/TrafficManager/AzureRM.TrafficManager.psd1 b/src/ResourceManager/TrafficManager/AzureRM.TrafficManager.psd1 index 6c947ff4fd50..53c26091e107 100644 --- a/src/ResourceManager/TrafficManager/AzureRM.TrafficManager.psd1 +++ b/src/ResourceManager/TrafficManager/AzureRM.TrafficManager.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/TrafficManager/Commands.TrafficManager2.Test/packages.config b/src/ResourceManager/TrafficManager/Commands.TrafficManager2.Test/packages.config index 74f196adcaea..34899424547c 100644 --- a/src/ResourceManager/TrafficManager/Commands.TrafficManager2.Test/packages.config +++ b/src/ResourceManager/TrafficManager/Commands.TrafficManager2.Test/packages.config @@ -16,7 +16,7 @@ - + diff --git a/src/ResourceManager/TrafficManager/Commands.TrafficManager2/Microsoft.Azure.Commands.TrafficManager.dll-help.psd1 b/src/ResourceManager/TrafficManager/Commands.TrafficManager2/Microsoft.Azure.Commands.TrafficManager.dll-help.psd1 index 468f29e6f2ce..b94eab87b356 100644 --- a/src/ResourceManager/TrafficManager/Commands.TrafficManager2/Microsoft.Azure.Commands.TrafficManager.dll-help.psd1 +++ b/src/ResourceManager/TrafficManager/Commands.TrafficManager2/Microsoft.Azure.Commands.TrafficManager.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/UsageAggregates/AzureRM.UsageAggregates.psd1 b/src/ResourceManager/UsageAggregates/AzureRM.UsageAggregates.psd1 index 856685283695..4a6070c86e06 100644 --- a/src/ResourceManager/UsageAggregates/AzureRM.UsageAggregates.psd1 +++ b/src/ResourceManager/UsageAggregates/AzureRM.UsageAggregates.psd1 @@ -85,6 +85,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/UsageAggregates/Commands.UsageAggregates/Microsoft.Azure.Commands.UsageAggregates.dll-help.psd1 b/src/ResourceManager/UsageAggregates/Commands.UsageAggregates/Microsoft.Azure.Commands.UsageAggregates.dll-help.psd1 index 37af85403660..e24758af6c71 100644 --- a/src/ResourceManager/UsageAggregates/Commands.UsageAggregates/Microsoft.Azure.Commands.UsageAggregates.dll-help.psd1 +++ b/src/ResourceManager/UsageAggregates/Commands.UsageAggregates/Microsoft.Azure.Commands.UsageAggregates.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Websites/AzureRM.Websites.psd1 b/src/ResourceManager/Websites/AzureRM.Websites.psd1 index d3c3df396ca5..3610a87d13e4 100644 --- a/src/ResourceManager/Websites/AzureRM.Websites.psd1 +++ b/src/ResourceManager/Websites/AzureRM.Websites.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ResourceManager/Websites/Commands.Websites.Test/Commands.Websites.Test.csproj b/src/ResourceManager/Websites/Commands.Websites.Test/Commands.Websites.Test.csproj index ad19d6a18c15..97b9560dda65 100644 --- a/src/ResourceManager/Websites/Commands.Websites.Test/Commands.Websites.Test.csproj +++ b/src/ResourceManager/Websites/Commands.Websites.Test/Commands.Websites.Test.csproj @@ -98,7 +98,7 @@ True - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ResourceManager/Websites/Commands.Websites.Test/packages.config b/src/ResourceManager/Websites/Commands.Websites.Test/packages.config index a75ff05d594c..c72673756034 100644 --- a/src/ResourceManager/Websites/Commands.Websites.Test/packages.config +++ b/src/ResourceManager/Websites/Commands.Websites.Test/packages.config @@ -17,7 +17,7 @@ - + diff --git a/src/ResourceManager/Websites/Commands.Websites/Microsoft.Azure.Commands.Websites.dll-Help.psd1 b/src/ResourceManager/Websites/Commands.Websites/Microsoft.Azure.Commands.Websites.dll-Help.psd1 index 77cb14b1eaad..b11eda3acbf3 100644 --- a/src/ResourceManager/Websites/Commands.Websites/Microsoft.Azure.Commands.Websites.dll-Help.psd1 +++ b/src/ResourceManager/Websites/Commands.Websites/Microsoft.Azure.Commands.Websites.dll-Help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj b/src/ServiceManagement/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj index 6bdf6547358f..c527fbf83935 100644 --- a/src/ServiceManagement/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj +++ b/src/ServiceManagement/Automation/Commands.Automation.Test/Commands.Automation.Test.csproj @@ -101,9 +101,9 @@ False ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/Automation/Commands.Automation.Test/packages.config b/src/ServiceManagement/Automation/Commands.Automation.Test/packages.config index eccff93afc3e..c242ff14f6e8 100644 --- a/src/ServiceManagement/Automation/Commands.Automation.Test/packages.config +++ b/src/ServiceManagement/Automation/Commands.Automation.Test/packages.config @@ -13,7 +13,7 @@ - + diff --git a/src/ServiceManagement/Automation/Commands.Automation/Microsoft.Azure.Commands.Automation.dll-help.psd1 b/src/ServiceManagement/Automation/Commands.Automation/Microsoft.Azure.Commands.Automation.dll-help.psd1 index 9bcf63596c99..96bf29917391 100644 --- a/src/ServiceManagement/Automation/Commands.Automation/Microsoft.Azure.Commands.Automation.dll-help.psd1 +++ b/src/ServiceManagement/Automation/Commands.Automation/Microsoft.Azure.Commands.Automation.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Common/Commands.Common.Test/Commands.Common.Test.csproj b/src/ServiceManagement/Common/Commands.Common.Test/Commands.Common.Test.csproj index bd055e8557dd..cec9f6ce69da 100644 --- a/src/ServiceManagement/Common/Commands.Common.Test/Commands.Common.Test.csproj +++ b/src/ServiceManagement/Common/Commands.Common.Test/Commands.Common.Test.csproj @@ -133,9 +133,9 @@ False ..\..\..\packages\WindowsAzure.Storage.6.1.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ServiceManagement/Common/Commands.Common.Test/packages.config b/src/ServiceManagement/Common/Commands.Common.Test/packages.config index e0a4eee362dc..0595cacba18b 100644 --- a/src/ServiceManagement/Common/Commands.Common.Test/packages.config +++ b/src/ServiceManagement/Common/Commands.Common.Test/packages.config @@ -21,7 +21,7 @@ - + diff --git a/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ProfileClient.cs b/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ProfileClient.cs index 42067d20c876..ecc7f2571033 100644 --- a/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ProfileClient.cs +++ b/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ProfileClient.cs @@ -654,7 +654,7 @@ public AzureSubscription SetSubscriptionAsDefault(Guid id, string accountName) { if (subscription.IsPropertySet(AzureSubscription.Property.StorageAccount)) { - ServiceManagementUtilities.ClearCurrentStorageAccount(); + Microsoft.WindowsAzure.Commands.Utilities.Common.GeneralUtilities.ClearCurrentStorageAccount(); } Profile.DefaultSubscription = subscription; diff --git a/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ServiceManagementUtilities.cs b/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ServiceManagementUtilities.cs index 8fb676d80c91..9ab247b13010 100644 --- a/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ServiceManagementUtilities.cs +++ b/src/ServiceManagement/Common/Commands.ServiceManagement.Common/ServiceManagementUtilities.cs @@ -51,30 +51,5 @@ public static void EnsureDefaultProfileDirectoryExists() AzureSession.DataStore.CreateDirectory(AzureSession.ProfileDirectory); } } - - /// - /// Clear the current storage account from the context - guarantees that only one storage account will be active - /// at a time. - /// - public static void ClearCurrentStorageAccount() - { - //TODO: Move to RM - //var RMProfile = AzureRmProfileProvider.Instance.Profile; - //if (RMProfile != null && RMProfile.Context != null && - // RMProfile.Context.Subscription != null && RMProfile.Context.Subscription.IsPropertySet(AzureSubscription.Property.StorageAccount)) - //{ - // RMProfile.Context.Subscription.SetProperty(AzureSubscription.Property.StorageAccount, null); - //} - - var SMProfile = AzureSMProfileProvider.Instance.Profile; - if (SMProfile != null && SMProfile.Context != null - && SMProfile.Context.Subscription != null && - SMProfile.Context.Subscription.IsPropertySet( - AzureSubscription.Property.StorageAccount)) - { - SMProfile.Context.Subscription.SetProperty( - AzureSubscription.Property.StorageAccount, null); - } - } } } diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.psd1 b/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.psd1 index 02cd21741262..ecf9bb73266e 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.psd1 +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/Microsoft.WindowsAzure.Commands.ServiceManagement.PlatformImageRepository.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/PIR.psd1 b/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/PIR.psd1 index 8b365e4fa7a1..6fe8e7d6017b 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/PIR.psd1 +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.PlatformImageRepository/PIR.psd1 @@ -86,7 +86,28 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/AzurePreview.psd1 b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/AzurePreview.psd1 index bbcd664e4c7b..acdcd3fd0a21 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/AzurePreview.psd1 +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/AzurePreview.psd1 @@ -87,7 +87,28 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js index fc4d43f90c02..a95998c6fa21 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.Preview/Generated/cli.js @@ -103,10 +103,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.changeConfigurationByName(serviceName, deploymentName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentChangeConfigurationByNamechangeConfigurationByNameParameters2 = deploymentChangeConfigurationByName.category('change-configuration-by-name-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentChangeConfigurationByNamechangeConfigurationByNameParameters2.command('generate') .description($('Generate deploymentChangeConfigurationByName parameter string or files.')) .usage('[options]') @@ -171,11 +173,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters set deployment-change-configuration-parameters 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 parameter for your deployment.')); - var setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); + setparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters0.command('deployment-change-configuration-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -264,11 +266,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters remove deployment-change-configuration-parameters 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 parameter for your deployment.')); - var removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); + removeparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters1.command('deployment-change-configuration-parameters') + .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.')) .option('--configuration', $('Remove the configuration value.')) @@ -328,11 +330,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters add deployment-change-configuration-parameters 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); + addparametersChangeConfigurationByNameDeploymentDeploymentChangeConfigurationParameters2.command('deployment-change-configuration-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -422,73 +424,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //change-configuration-by-name-parameters set extension-configuration - var catparametersChangeConfigurationByNameDeploymentExtensionConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersChangeConfigurationByNameDeploymentExtensionConfiguration0 = catparametersChangeConfigurationByNameDeploymentExtensionConfiguration0.category('change-configuration-by-name-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersChangeConfigurationByNameDeploymentExtensionConfiguration0 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration0.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-name-parameters file.')); - setparametersChangeConfigurationByNameDeploymentExtensionConfiguration0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--all-roles ', $('Set the all-roles value.')) - .option('--named-roles ', $('Set the named-roles value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/extensionConfiguration'; - var paramPath = options.path + '/' + 'allRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.allRoles) { - if (options.parse && options.allRoles) { - options.allRoles = JSON.parse(options.allRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.allRoles}]); - } - paramPath = options.path + '/' + 'namedRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.namedRoles) { - if (options.parse && options.namedRoles) { - options.namedRoles = JSON.parse(options.namedRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.namedRoles}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //change-configuration-by-name-parameters remove extension-configuration 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 parameter for your deployment.')); - var removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration1.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); + removeparametersChangeConfigurationByNameDeploymentExtensionConfiguration1.command('extension-configuration') + .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.')) .option('--all-roles', $('Remove the all-roles value.')) @@ -533,11 +476,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters add extension-configuration 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration2.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2 = parametersChangeConfigurationByNameDeploymentExtensionConfiguration2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); + addparametersChangeConfigurationByNameDeploymentExtensionConfiguration2.command('extension-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -596,11 +539,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters set all-roles 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 parameter for your deployment.')); - var setparametersChangeConfigurationByNameDeploymentAllRoles0 = parametersChangeConfigurationByNameDeploymentAllRoles0.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationByNameDeploymentAllRoles0 = parametersChangeConfigurationByNameDeploymentAllRoles0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); + setparametersChangeConfigurationByNameDeploymentAllRoles0.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -660,11 +603,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters remove all-roles 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 parameter for your deployment.')); - var removeparametersChangeConfigurationByNameDeploymentAllRoles1 = parametersChangeConfigurationByNameDeploymentAllRoles1.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationByNameDeploymentAllRoles1 = parametersChangeConfigurationByNameDeploymentAllRoles1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); + removeparametersChangeConfigurationByNameDeploymentAllRoles1.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -710,11 +653,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters add all-roles 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationByNameDeploymentAllRoles2 = parametersChangeConfigurationByNameDeploymentAllRoles2.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationByNameDeploymentAllRoles2 = parametersChangeConfigurationByNameDeploymentAllRoles2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); + addparametersChangeConfigurationByNameDeploymentAllRoles2.command('all-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -773,11 +716,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters set named-roles 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 parameter for your deployment.')); - var setparametersChangeConfigurationByNameDeploymentNamedRoles0 = parametersChangeConfigurationByNameDeploymentNamedRoles0.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationByNameDeploymentNamedRoles0 = parametersChangeConfigurationByNameDeploymentNamedRoles0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); + setparametersChangeConfigurationByNameDeploymentNamedRoles0.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -837,11 +780,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters remove named-roles 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 parameter for your deployment.')); - var removeparametersChangeConfigurationByNameDeploymentNamedRoles1 = parametersChangeConfigurationByNameDeploymentNamedRoles1.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationByNameDeploymentNamedRoles1 = parametersChangeConfigurationByNameDeploymentNamedRoles1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); + removeparametersChangeConfigurationByNameDeploymentNamedRoles1.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -887,11 +830,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters add named-roles 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationByNameDeploymentNamedRoles2 = parametersChangeConfigurationByNameDeploymentNamedRoles2.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationByNameDeploymentNamedRoles2 = parametersChangeConfigurationByNameDeploymentNamedRoles2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); + addparametersChangeConfigurationByNameDeploymentNamedRoles2.command('named-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -950,11 +893,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters set extensions 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 parameter for your deployment.')); - var setparametersChangeConfigurationByNameDeploymentExtensions0 = parametersChangeConfigurationByNameDeploymentExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationByNameDeploymentExtensions0 = parametersChangeConfigurationByNameDeploymentExtensions0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-name-parameters file.')); + setparametersChangeConfigurationByNameDeploymentExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -993,11 +936,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters remove extensions 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 parameter for your deployment.')); - var removeparametersChangeConfigurationByNameDeploymentExtensions1 = parametersChangeConfigurationByNameDeploymentExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationByNameDeploymentExtensions1 = parametersChangeConfigurationByNameDeploymentExtensions1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-name-parameters file.')); + removeparametersChangeConfigurationByNameDeploymentExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1028,11 +971,11 @@ exports.init = function (cli) { //change-configuration-by-name-parameters add extensions 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationByNameDeploymentExtensions2 = parametersChangeConfigurationByNameDeploymentExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationByNameDeploymentExtensions2 = parametersChangeConfigurationByNameDeploymentExtensions2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-name-parameters file.')); + addparametersChangeConfigurationByNameDeploymentExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -1135,10 +1078,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.changeConfigurationBySlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentChangeConfigurationBySlotchangeConfigurationBySlotParameters2 = deploymentChangeConfigurationBySlot.category('change-configuration-by-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentChangeConfigurationBySlotchangeConfigurationBySlotParameters2.command('generate') .description($('Generate deploymentChangeConfigurationBySlot parameter string or files.')) .usage('[options]') @@ -1203,11 +1148,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters set deployment-change-configuration-parameters 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 parameter for your deployment.')); - var setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); + setparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters0.command('deployment-change-configuration-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -1296,11 +1241,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters remove deployment-change-configuration-parameters 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 parameter for your deployment.')); - var removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); + removeparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters1.command('deployment-change-configuration-parameters') + .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.')) .option('--configuration', $('Remove the configuration value.')) @@ -1360,11 +1305,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters add deployment-change-configuration-parameters 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.category('deployment-change-configuration-parameters') - .description($('Commands to set/remove/add deployment-change-configuration-parameters of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2 = parametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); + addparametersChangeConfigurationBySlotDeploymentDeploymentChangeConfigurationParameters2.command('deployment-change-configuration-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -1454,73 +1399,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //change-configuration-by-slot-parameters set extension-configuration - var catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersChangeConfigurationBySlotDeploymentExtensionConfiguration0 = catparametersChangeConfigurationBySlotDeploymentExtensionConfiguration0.category('change-configuration-by-slot-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersChangeConfigurationBySlotDeploymentExtensionConfiguration0 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration0.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-slot-parameters file.')); - setparametersChangeConfigurationBySlotDeploymentExtensionConfiguration0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--all-roles ', $('Set the all-roles value.')) - .option('--named-roles ', $('Set the named-roles value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/extensionConfiguration'; - var paramPath = options.path + '/' + 'allRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.allRoles) { - if (options.parse && options.allRoles) { - options.allRoles = JSON.parse(options.allRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.allRoles}]); - } - paramPath = options.path + '/' + 'namedRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.namedRoles) { - if (options.parse && options.namedRoles) { - options.namedRoles = JSON.parse(options.namedRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.namedRoles}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //change-configuration-by-slot-parameters remove extension-configuration 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 parameter for your deployment.')); - var removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); + removeparametersChangeConfigurationBySlotDeploymentExtensionConfiguration1.command('extension-configuration') + .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.')) .option('--all-roles', $('Remove the all-roles value.')) @@ -1565,11 +1451,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters add extension-configuration 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2 = parametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); + addparametersChangeConfigurationBySlotDeploymentExtensionConfiguration2.command('extension-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -1628,11 +1514,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters set all-roles 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 parameter for your deployment.')); - var setparametersChangeConfigurationBySlotDeploymentAllRoles0 = parametersChangeConfigurationBySlotDeploymentAllRoles0.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationBySlotDeploymentAllRoles0 = parametersChangeConfigurationBySlotDeploymentAllRoles0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); + setparametersChangeConfigurationBySlotDeploymentAllRoles0.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1692,11 +1578,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters remove all-roles 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 parameter for your deployment.')); - var removeparametersChangeConfigurationBySlotDeploymentAllRoles1 = parametersChangeConfigurationBySlotDeploymentAllRoles1.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationBySlotDeploymentAllRoles1 = parametersChangeConfigurationBySlotDeploymentAllRoles1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); + removeparametersChangeConfigurationBySlotDeploymentAllRoles1.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1742,11 +1628,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters add all-roles 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationBySlotDeploymentAllRoles2 = parametersChangeConfigurationBySlotDeploymentAllRoles2.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationBySlotDeploymentAllRoles2 = parametersChangeConfigurationBySlotDeploymentAllRoles2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); + addparametersChangeConfigurationBySlotDeploymentAllRoles2.command('all-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -1805,11 +1691,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters set named-roles 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 parameter for your deployment.')); - var setparametersChangeConfigurationBySlotDeploymentNamedRoles0 = parametersChangeConfigurationBySlotDeploymentNamedRoles0.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationBySlotDeploymentNamedRoles0 = parametersChangeConfigurationBySlotDeploymentNamedRoles0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); + setparametersChangeConfigurationBySlotDeploymentNamedRoles0.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1869,11 +1755,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters remove named-roles 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 parameter for your deployment.')); - var removeparametersChangeConfigurationBySlotDeploymentNamedRoles1 = parametersChangeConfigurationBySlotDeploymentNamedRoles1.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationBySlotDeploymentNamedRoles1 = parametersChangeConfigurationBySlotDeploymentNamedRoles1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); + removeparametersChangeConfigurationBySlotDeploymentNamedRoles1.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -1919,11 +1805,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters add named-roles 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationBySlotDeploymentNamedRoles2 = parametersChangeConfigurationBySlotDeploymentNamedRoles2.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationBySlotDeploymentNamedRoles2 = parametersChangeConfigurationBySlotDeploymentNamedRoles2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); + addparametersChangeConfigurationBySlotDeploymentNamedRoles2.command('named-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -1982,11 +1868,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters set extensions 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 parameter for your deployment.')); - var setparametersChangeConfigurationBySlotDeploymentExtensions0 = parametersChangeConfigurationBySlotDeploymentExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersChangeConfigurationBySlotDeploymentExtensions0 = parametersChangeConfigurationBySlotDeploymentExtensions0.category('set') + .description($('Commands to set components of deployment in change-configuration-by-slot-parameters file.')); + setparametersChangeConfigurationBySlotDeploymentExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2025,11 +1911,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters remove extensions 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 parameter for your deployment.')); - var removeparametersChangeConfigurationBySlotDeploymentExtensions1 = parametersChangeConfigurationBySlotDeploymentExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersChangeConfigurationBySlotDeploymentExtensions1 = parametersChangeConfigurationBySlotDeploymentExtensions1.category('remove') + .description($('Commands to remove components of deployment in change-configuration-by-slot-parameters file.')); + removeparametersChangeConfigurationBySlotDeploymentExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2060,11 +1946,11 @@ exports.init = function (cli) { //change-configuration-by-slot-parameters add extensions 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 the parameter input file for your deployment.')); - var addparametersChangeConfigurationBySlotDeploymentExtensions2 = parametersChangeConfigurationBySlotDeploymentExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in change-configuration-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersChangeConfigurationBySlotDeploymentExtensions2 = parametersChangeConfigurationBySlotDeploymentExtensions2.category('add') + .description($('Commands to add components of deployment in change-configuration-by-slot-parameters file.')); + addparametersChangeConfigurationBySlotDeploymentExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -2170,10 +2056,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.create(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentCreatecreateParameters2 = deploymentCreate.category('create-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentCreatecreateParameters2.command('generate') .description($('Generate deploymentCreate parameter string or files.')) .usage('[options]') @@ -2238,11 +2126,11 @@ exports.init = function (cli) { //create-parameters set deployment-create-parameters var catparametersCreateDeploymentDeploymentCreateParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters0 = catparametersCreateDeploymentDeploymentCreateParameters0.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersCreateDeploymentDeploymentCreateParameters0 = parametersCreateDeploymentDeploymentCreateParameters0.category('deployment-create-parameters') - .description($('Commands to set/remove/add deployment-create-parameters of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersCreateDeploymentDeploymentCreateParameters0 = parametersCreateDeploymentDeploymentCreateParameters0.category('set') + .description($('Commands to set components of deployment in create-parameters file.')); + setparametersCreateDeploymentDeploymentCreateParameters0.command('deployment-create-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -2365,11 +2253,11 @@ exports.init = function (cli) { //create-parameters remove deployment-create-parameters var catparametersCreateDeploymentDeploymentCreateParameters1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters1 = catparametersCreateDeploymentDeploymentCreateParameters1.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var removeparametersCreateDeploymentDeploymentCreateParameters1 = parametersCreateDeploymentDeploymentCreateParameters1.category('deployment-create-parameters') - .description($('Commands to set/remove/add deployment-create-parameters of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersCreateDeploymentDeploymentCreateParameters1 = parametersCreateDeploymentDeploymentCreateParameters1.category('remove') + .description($('Commands to remove components of deployment in create-parameters file.')); + removeparametersCreateDeploymentDeploymentCreateParameters1.command('deployment-create-parameters') + .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.')) .option('--configuration', $('Remove the configuration value.')) @@ -2444,11 +2332,11 @@ exports.init = function (cli) { //create-parameters add deployment-create-parameters var catparametersCreateDeploymentDeploymentCreateParameters2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentDeploymentCreateParameters2 = catparametersCreateDeploymentDeploymentCreateParameters2.category('create-parameters') - .description($('Commands to manage the parameter input file for your deployment.')); - var addparametersCreateDeploymentDeploymentCreateParameters2 = parametersCreateDeploymentDeploymentCreateParameters2.category('deployment-create-parameters') - .description($('Commands to set/remove/add deployment-create-parameters of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersCreateDeploymentDeploymentCreateParameters2 = parametersCreateDeploymentDeploymentCreateParameters2.category('add') + .description($('Commands to add components of deployment in create-parameters file.')); + addparametersCreateDeploymentDeploymentCreateParameters2.command('deployment-create-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -2572,73 +2460,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //create-parameters set extension-configuration - var catparametersCreateDeploymentExtensionConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersCreateDeploymentExtensionConfiguration0 = catparametersCreateDeploymentExtensionConfiguration0.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersCreateDeploymentExtensionConfiguration0 = parametersCreateDeploymentExtensionConfiguration0.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in create-parameters file.')); - setparametersCreateDeploymentExtensionConfiguration0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--all-roles ', $('Set the all-roles value.')) - .option('--named-roles ', $('Set the named-roles value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/extensionConfiguration'; - var paramPath = options.path + '/' + 'allRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.allRoles) { - if (options.parse && options.allRoles) { - options.allRoles = JSON.parse(options.allRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.allRoles}]); - } - paramPath = options.path + '/' + 'namedRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.namedRoles) { - if (options.parse && options.namedRoles) { - options.namedRoles = JSON.parse(options.namedRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.namedRoles}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //create-parameters remove extension-configuration var catparametersCreateDeploymentExtensionConfiguration1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensionConfiguration1 = catparametersCreateDeploymentExtensionConfiguration1.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var removeparametersCreateDeploymentExtensionConfiguration1 = parametersCreateDeploymentExtensionConfiguration1.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersCreateDeploymentExtensionConfiguration1 = parametersCreateDeploymentExtensionConfiguration1.category('remove') + .description($('Commands to remove components of deployment in create-parameters file.')); + removeparametersCreateDeploymentExtensionConfiguration1.command('extension-configuration') + .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.')) .option('--all-roles', $('Remove the all-roles value.')) @@ -2683,11 +2512,11 @@ exports.init = function (cli) { //create-parameters add extension-configuration var catparametersCreateDeploymentExtensionConfiguration2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensionConfiguration2 = catparametersCreateDeploymentExtensionConfiguration2.category('create-parameters') - .description($('Commands to manage the parameter input file for your deployment.')); - var addparametersCreateDeploymentExtensionConfiguration2 = parametersCreateDeploymentExtensionConfiguration2.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersCreateDeploymentExtensionConfiguration2 = parametersCreateDeploymentExtensionConfiguration2.category('add') + .description($('Commands to add components of deployment in create-parameters file.')); + addparametersCreateDeploymentExtensionConfiguration2.command('extension-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -2746,11 +2575,11 @@ exports.init = function (cli) { //create-parameters set all-roles var catparametersCreateDeploymentAllRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles0 = catparametersCreateDeploymentAllRoles0.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersCreateDeploymentAllRoles0 = parametersCreateDeploymentAllRoles0.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersCreateDeploymentAllRoles0 = parametersCreateDeploymentAllRoles0.category('set') + .description($('Commands to set components of deployment in create-parameters file.')); + setparametersCreateDeploymentAllRoles0.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2810,11 +2639,11 @@ exports.init = function (cli) { //create-parameters remove all-roles var catparametersCreateDeploymentAllRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles1 = catparametersCreateDeploymentAllRoles1.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var removeparametersCreateDeploymentAllRoles1 = parametersCreateDeploymentAllRoles1.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersCreateDeploymentAllRoles1 = parametersCreateDeploymentAllRoles1.category('remove') + .description($('Commands to remove components of deployment in create-parameters file.')); + removeparametersCreateDeploymentAllRoles1.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2860,11 +2689,11 @@ exports.init = function (cli) { //create-parameters add all-roles var catparametersCreateDeploymentAllRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentAllRoles2 = catparametersCreateDeploymentAllRoles2.category('create-parameters') - .description($('Commands to manage the parameter input file for your deployment.')); - var addparametersCreateDeploymentAllRoles2 = parametersCreateDeploymentAllRoles2.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersCreateDeploymentAllRoles2 = parametersCreateDeploymentAllRoles2.category('add') + .description($('Commands to add components of deployment in create-parameters file.')); + addparametersCreateDeploymentAllRoles2.command('all-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -2923,11 +2752,11 @@ exports.init = function (cli) { //create-parameters set named-roles var catparametersCreateDeploymentNamedRoles0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles0 = catparametersCreateDeploymentNamedRoles0.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersCreateDeploymentNamedRoles0 = parametersCreateDeploymentNamedRoles0.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersCreateDeploymentNamedRoles0 = parametersCreateDeploymentNamedRoles0.category('set') + .description($('Commands to set components of deployment in create-parameters file.')); + setparametersCreateDeploymentNamedRoles0.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -2987,11 +2816,11 @@ exports.init = function (cli) { //create-parameters remove named-roles var catparametersCreateDeploymentNamedRoles1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles1 = catparametersCreateDeploymentNamedRoles1.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var removeparametersCreateDeploymentNamedRoles1 = parametersCreateDeploymentNamedRoles1.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersCreateDeploymentNamedRoles1 = parametersCreateDeploymentNamedRoles1.category('remove') + .description($('Commands to remove components of deployment in create-parameters file.')); + removeparametersCreateDeploymentNamedRoles1.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3037,11 +2866,11 @@ exports.init = function (cli) { //create-parameters add named-roles var catparametersCreateDeploymentNamedRoles2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentNamedRoles2 = catparametersCreateDeploymentNamedRoles2.category('create-parameters') - .description($('Commands to manage the parameter input file for your deployment.')); - var addparametersCreateDeploymentNamedRoles2 = parametersCreateDeploymentNamedRoles2.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersCreateDeploymentNamedRoles2 = parametersCreateDeploymentNamedRoles2.category('add') + .description($('Commands to add components of deployment in create-parameters file.')); + addparametersCreateDeploymentNamedRoles2.command('named-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -3100,11 +2929,11 @@ exports.init = function (cli) { //create-parameters set extensions var catparametersCreateDeploymentExtensions0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions0 = catparametersCreateDeploymentExtensions0.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersCreateDeploymentExtensions0 = parametersCreateDeploymentExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersCreateDeploymentExtensions0 = parametersCreateDeploymentExtensions0.category('set') + .description($('Commands to set components of deployment in create-parameters file.')); + setparametersCreateDeploymentExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3143,11 +2972,11 @@ exports.init = function (cli) { //create-parameters remove extensions var catparametersCreateDeploymentExtensions1 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions1 = catparametersCreateDeploymentExtensions1.category('create-parameters') - .description($('Commands to manage parameter for your deployment.')); - var removeparametersCreateDeploymentExtensions1 = parametersCreateDeploymentExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersCreateDeploymentExtensions1 = parametersCreateDeploymentExtensions1.category('remove') + .description($('Commands to remove components of deployment in create-parameters file.')); + removeparametersCreateDeploymentExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3178,11 +3007,11 @@ exports.init = function (cli) { //create-parameters add extensions var catparametersCreateDeploymentExtensions2 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); var parametersCreateDeploymentExtensions2 = catparametersCreateDeploymentExtensions2.category('create-parameters') - .description($('Commands to manage the parameter input file for your deployment.')); - var addparametersCreateDeploymentExtensions2 = parametersCreateDeploymentExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in create-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersCreateDeploymentExtensions2 = parametersCreateDeploymentExtensions2.category('add') + .description($('Commands to add components of deployment in create-parameters file.')); + addparametersCreateDeploymentExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -3256,7 +3085,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.deleteByName(serviceName, deploymentName, deleteFromStorage, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment DeleteBySlot @@ -3288,7 +3119,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.deleteBySlot(serviceName, deploymentSlot, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment DeleteRoleInstanceByDeploymentName @@ -3331,7 +3164,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.deleteRoleInstanceByDeploymentName(serviceName, deploymentName, roleInstanceName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment DeleteRoleInstanceByDeploymentSlot @@ -3374,8 +3209,8 @@ exports.init = function (cli) { parametersObj = JSON.parse(fileContent); } else { - var parametersValArr = parameters.split(','); - cli.output.verbose('parametersValArr : ' + parametersValArr); + var parametersValArr = parameters ? parameters.split(',') : []; + cli.output.verbose('parameters : ' + parametersValArr); parametersObj = []; for (var item in parametersValArr) { parametersObj.push(parametersValArr[item]); @@ -3385,10 +3220,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.deleteRoleInstanceByDeploymentSlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentDeleteRoleInstanceByDeploymentSlotdeleteRoleInstanceByDeploymentSlotParameters2 = deploymentDeleteRoleInstanceByDeploymentSlot.category('delete-role-instance-by-deployment-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentDeleteRoleInstanceByDeploymentSlotdeleteRoleInstanceByDeploymentSlotParameters2.command('generate') .description($('Generate deploymentDeleteRoleInstanceByDeploymentSlot parameter string or files.')) .usage('[options]') @@ -3453,11 +3290,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters set deployment-delete-role-instance-parameters 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 parameter for your deployment.')); - var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.category('deployment-delete-role-instance-parameters') - .description($('Commands to set/remove/add deployment-delete-role-instance-parameters of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.category('set') + .description($('Commands to set components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + setparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters0.command('deployment-delete-role-instance-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -3501,11 +3338,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters remove deployment-delete-role-instance-parameters 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 parameter for your deployment.')); - var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.category('deployment-delete-role-instance-parameters') - .description($('Commands to set/remove/add deployment-delete-role-instance-parameters of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.category('remove') + .description($('Commands to remove components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters1.command('deployment-delete-role-instance-parameters') + .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.')) .option('--name', $('Remove the name value.')) @@ -3545,11 +3382,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters add deployment-delete-role-instance-parameters 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 the parameter input file for your deployment.')); - var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.category('deployment-delete-role-instance-parameters') - .description($('Commands to set/remove/add deployment-delete-role-instance-parameters of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.category('add') + .description($('Commands to add components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + addparametersDeleteRoleInstanceByDeploymentSlotDeploymentDeploymentDeleteRoleInstanceParameters2.command('deployment-delete-role-instance-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -3597,11 +3434,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters set name 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 parameter for your deployment.')); - var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.category('name') - .description($('Commands to set/remove/add name of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.category('set') + .description($('Commands to set components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + setparametersDeleteRoleInstanceByDeploymentSlotDeploymentName0.command('name') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3639,11 +3476,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters remove name 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 parameter for your deployment.')); - var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.category('name') - .description($('Commands to set/remove/add name of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.category('remove') + .description($('Commands to remove components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + removeparametersDeleteRoleInstanceByDeploymentSlotDeploymentName1.command('name') + .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.')) .option('--index ', $('Indexer: index.')) @@ -3673,11 +3510,11 @@ exports.init = function (cli) { //delete-role-instance-by-deployment-slot-parameters add name 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 the parameter input file for your deployment.')); - var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.category('name') - .description($('Commands to set/remove/add name of deployment in delete-role-instance-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2 = parametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.category('add') + .description($('Commands to add components of deployment in delete-role-instance-by-deployment-slot-parameters file.')); + addparametersDeleteRoleInstanceByDeploymentSlotDeploymentName2.command('name') + .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.')) .option('--key ', $('The JSON key.')) @@ -3740,7 +3577,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.getByName(serviceName, deploymentName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment GetBySlot @@ -3772,7 +3611,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.getBySlot(serviceName, deploymentSlot, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment GetPackageByName @@ -3820,10 +3661,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.getPackageByName(serviceName, deploymentName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentGetPackageByNamegetPackageByNameParameters2 = deploymentGetPackageByName.category('get-package-by-name-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentGetPackageByNamegetPackageByNameParameters2.command('generate') .description($('Generate deploymentGetPackageByName parameter string or files.')) .usage('[options]') @@ -3888,11 +3731,11 @@ exports.init = function (cli) { //get-package-by-name-parameters set deployment-get-package-parameters 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 parameter for your deployment.')); - var setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.category('set') + .description($('Commands to set components of deployment in get-package-by-name-parameters file.')); + setparametersGetPackageByNameDeploymentDeploymentGetPackageParameters0.command('deployment-get-package-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -3948,11 +3791,11 @@ exports.init = function (cli) { //get-package-by-name-parameters remove deployment-get-package-parameters 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 parameter for your deployment.')); - var removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.category('remove') + .description($('Commands to remove components of deployment in get-package-by-name-parameters file.')); + removeparametersGetPackageByNameDeploymentDeploymentGetPackageParameters1.command('deployment-get-package-parameters') + .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.')) .option('--container-uri', $('Remove the container-uri value.')) @@ -3997,11 +3840,11 @@ exports.init = function (cli) { //get-package-by-name-parameters add deployment-get-package-parameters 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 the parameter input file for your deployment.')); - var addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2 = parametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.category('add') + .description($('Commands to add components of deployment in get-package-by-name-parameters file.')); + addparametersGetPackageByNameDeploymentDeploymentGetPackageParameters2.command('deployment-get-package-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -4105,10 +3948,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.getPackageBySlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentGetPackageBySlotgetPackageBySlotParameters2 = deploymentGetPackageBySlot.category('get-package-by-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentGetPackageBySlotgetPackageBySlotParameters2.command('generate') .description($('Generate deploymentGetPackageBySlot parameter string or files.')) .usage('[options]') @@ -4173,11 +4018,11 @@ exports.init = function (cli) { //get-package-by-slot-parameters set deployment-get-package-parameters 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 parameter for your deployment.')); - var setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.category('set') + .description($('Commands to set components of deployment in get-package-by-slot-parameters file.')); + setparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters0.command('deployment-get-package-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -4233,11 +4078,11 @@ exports.init = function (cli) { //get-package-by-slot-parameters remove deployment-get-package-parameters 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 parameter for your deployment.')); - var removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.category('remove') + .description($('Commands to remove components of deployment in get-package-by-slot-parameters file.')); + removeparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters1.command('deployment-get-package-parameters') + .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.')) .option('--container-uri', $('Remove the container-uri value.')) @@ -4282,11 +4127,11 @@ exports.init = function (cli) { //get-package-by-slot-parameters add deployment-get-package-parameters 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 the parameter input file for your deployment.')); - var addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.category('deployment-get-package-parameters') - .description($('Commands to set/remove/add deployment-get-package-parameters of deployment in get-package-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2 = parametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.category('add') + .description($('Commands to add components of deployment in get-package-by-slot-parameters file.')); + addparametersGetPackageBySlotDeploymentDeploymentGetPackageParameters2.command('deployment-get-package-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -4386,7 +4231,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.listEvents(serviceName, deploymentName, startTime, endTime, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment ListEventsBySlot @@ -4432,7 +4279,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.listEventsBySlot(serviceName, deploymentSlot, startTime, endTime, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment RebootRoleInstanceByDeploymentName @@ -4469,7 +4318,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rebootRoleInstanceByDeploymentName(serviceName, deploymentName, roleInstanceName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment RebootRoleInstanceByDeploymentSlot @@ -4508,7 +4359,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rebootRoleInstanceByDeploymentSlot(serviceName, deploymentSlot, roleInstanceName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment RebuildRoleInstanceByDeploymentName @@ -4552,7 +4405,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rebuildRoleInstanceByDeploymentName(serviceName, deploymentName, roleInstanceName, resources, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment RebuildRoleInstanceByDeploymentSlot @@ -4596,7 +4451,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rebuildRoleInstanceByDeploymentSlot(serviceName, deploymentSlot, roleInstanceName, resources, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment ReimageRoleInstanceByDeploymentName @@ -4633,7 +4490,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.reimageRoleInstanceByDeploymentName(serviceName, deploymentName, roleInstanceName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment ReimageRoleInstanceByDeploymentSlot @@ -4672,7 +4531,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.reimageRoleInstanceByDeploymentSlot(serviceName, deploymentSlot, roleInstanceName, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment RollbackUpdateOrUpgradeByDeploymentName @@ -4720,10 +4581,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rollbackUpdateOrUpgradeByDeploymentName(serviceName, deploymentName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentRollbackUpdateOrUpgradeByDeploymentNamerollbackUpdateOrUpgradeByDeploymentNameParameters2 = deploymentRollbackUpdateOrUpgradeByDeploymentName.category('rollback-update-or-upgrade-by-deployment-name-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentRollbackUpdateOrUpgradeByDeploymentNamerollbackUpdateOrUpgradeByDeploymentNameParameters2.command('generate') .description($('Generate deploymentRollbackUpdateOrUpgradeByDeploymentName parameter string or files.')) .usage('[options]') @@ -4788,182 +4651,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-name-parameters set deployment-rollback-update-or-upgrade-parameters 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 parameter for your deployment.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--force ', $('Set the force value.')) - .option('--mode ', $('Set the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'force'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.force) { - if (options.parse && options.force) { - options.force = JSON.parse(options.force); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.force}]); - } - paramPath = options.path + '/' + 'mode'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.mode) { - if (options.parse && options.mode) { - options.mode = JSON.parse(options.mode); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.mode}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //rollback-update-or-upgrade-by-deployment-name-parameters remove deployment-rollback-update-or-upgrade-parameters - 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--force', $('Remove the force value.')) - .option('--mode', $('Remove the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'remove'; - options.path = ''; - var anySubItem = false || options.force || options.mode; - if (anySubItem) { - var subItemPath = null; - if (options.force) { - subItemPath = options.path + '/force'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - if (options.mode) { - subItemPath = options.path + '/mode'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - } - else { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); - } - - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //rollback-update-or-upgrade-by-deployment-name-parameters add deployment-rollback-update-or-upgrade-parameters - 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--key ', $('The JSON key.')) - .option('--value ', $('The JSON value.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--force ', $('Add the force value.')) - .option('--mode ', $('Add the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'add'; - options.path = '' + '/' + options.key; - cli.output.verbose('options.path = ' + options.path); - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - var paramPath = '' + '/' + 'force'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.force) { - if (options.parse && options.force) { - options.force = JSON.parse(options.force); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.force}]); - } - paramPath = '' + '/' + 'mode'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.mode) { - if (options.parse && options.mode) { - options.mode = JSON.parse(options.mode); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.mode}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //rollback-update-or-upgrade-by-deployment-name-parameters set deployment-rollback-update-or-upgrade-parameters - 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 parameter for your deployment.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('set') + .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') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -5018,11 +4710,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-name-parameters remove deployment-rollback-update-or-upgrade-parameters 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('remove') + .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') + .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.')) .option('--force', $('Remove the force value.')) @@ -5067,11 +4759,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-name-parameters add deployment-rollback-update-or-upgrade-parameters 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('add') + .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') + .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.')) .option('--key ', $('The JSON key.')) @@ -5130,11 +4822,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-name-parameters remove mode 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.category('mode') - .description($('Commands to set/remove/add mode of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.category('remove') + .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); + removeparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode1.command('mode') + .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.')) .execute(function(options, _) { @@ -5162,11 +4854,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-name-parameters add mode 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.category('mode') - .description($('Commands to set/remove/add mode of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.category('add') + .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-name-parameters file.')); + addparametersRollbackUpdateOrUpgradeByDeploymentNameDeploymentMode2.command('mode') + .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.')) .option('--key ', $('The JSON key.')) @@ -5247,10 +4939,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.rollbackUpdateOrUpgradeByDeploymentSlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentRollbackUpdateOrUpgradeByDeploymentSlotrollbackUpdateOrUpgradeByDeploymentSlotParameters2 = deploymentRollbackUpdateOrUpgradeByDeploymentSlot.category('rollback-update-or-upgrade-by-deployment-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentRollbackUpdateOrUpgradeByDeploymentSlotrollbackUpdateOrUpgradeByDeploymentSlotParameters2.command('generate') .description($('Generate deploymentRollbackUpdateOrUpgradeByDeploymentSlot parameter string or files.')) .usage('[options]') @@ -5315,11 +5009,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-slot-parameters set deployment-rollback-update-or-upgrade-parameters 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 parameter for your deployment.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('set') + .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') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -5374,11 +5068,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-slot-parameters remove deployment-rollback-update-or-upgrade-parameters 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('remove') + .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') + .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.')) .option('--force', $('Remove the force value.')) @@ -5423,182 +5117,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-slot-parameters add deployment-rollback-update-or-upgrade-parameters 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--key ', $('The JSON key.')) - .option('--value ', $('The JSON value.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--force ', $('Add the force value.')) - .option('--mode ', $('Add the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'add'; - options.path = '' + '/' + options.key; - cli.output.verbose('options.path = ' + options.path); - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - var paramPath = '' + '/' + 'force'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.force) { - if (options.parse && options.force) { - options.force = JSON.parse(options.force); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.force}]); - } - paramPath = '' + '/' + 'mode'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.mode) { - if (options.parse && options.mode) { - options.mode = JSON.parse(options.mode); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.mode}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //rollback-update-or-upgrade-by-deployment-slot-parameters set deployment-rollback-update-or-upgrade-parameters - 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 parameter for your deployment.')); - var setparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters0.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--force ', $('Set the force value.')) - .option('--mode ', $('Set the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'force'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.force) { - if (options.parse && options.force) { - options.force = JSON.parse(options.force); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.force}]); - } - paramPath = options.path + '/' + 'mode'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.mode) { - if (options.parse && options.mode) { - options.mode = JSON.parse(options.mode); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.mode}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //rollback-update-or-upgrade-by-deployment-slot-parameters remove deployment-rollback-update-or-upgrade-parameters - 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters1.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--force', $('Remove the force value.')) - .option('--mode', $('Remove the mode value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'remove'; - options.path = ''; - var anySubItem = false || options.force || options.mode; - if (anySubItem) { - var subItemPath = null; - if (options.force) { - subItemPath = options.path + '/force'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - if (options.mode) { - subItemPath = options.path + '/mode'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - } - else { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); - } - - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //rollback-update-or-upgrade-by-deployment-slot-parameters add deployment-rollback-update-or-upgrade-parameters - 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('deployment-rollback-update-or-upgrade-parameters') - .description($('Commands to set/remove/add deployment-rollback-update-or-upgrade-parameters of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentDeploymentRollbackUpdateOrUpgradeParameters2.category('add') + .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') + .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.')) .option('--key ', $('The JSON key.')) @@ -5657,11 +5180,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-slot-parameters remove mode 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 parameter for your deployment.')); - var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.category('mode') - .description($('Commands to set/remove/add mode of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.category('remove') + .description($('Commands to remove components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); + removeparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode1.command('mode') + .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.')) .execute(function(options, _) { @@ -5689,11 +5212,11 @@ exports.init = function (cli) { //rollback-update-or-upgrade-by-deployment-slot-parameters add mode 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 the parameter input file for your deployment.')); - var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.category('mode') - .description($('Commands to set/remove/add mode of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2 = parametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.category('add') + .description($('Commands to add components of deployment in rollback-update-or-upgrade-by-deployment-slot-parameters file.')); + addparametersRollbackUpdateOrUpgradeByDeploymentSlotDeploymentMode2.command('mode') + .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.')) .option('--key ', $('The JSON key.')) @@ -5771,7 +5294,9 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.swap(serviceName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); /* Deployment UpdateStatusByDeploymentName @@ -5818,10 +5343,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.updateStatusByDeploymentName(serviceName, deploymentName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentUpdateStatusByDeploymentNameupdateStatusByDeploymentNameParameters2 = deploymentUpdateStatusByDeploymentName.category('update-status-by-deployment-name-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentUpdateStatusByDeploymentNameupdateStatusByDeploymentNameParameters2.command('generate') .description($('Generate deploymentUpdateStatusByDeploymentName parameter string or files.')) .usage('[options]') @@ -5883,62 +5410,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //update-status-by-deployment-name-parameters set deployment-update-status-parameters - var catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.category('update-status-by-deployment-name-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - setparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Set the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //update-status-by-deployment-name-parameters remove deployment-update-status-parameters 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('remove') + .description($('Commands to remove components of deployment in update-status-by-deployment-name-parameters file.')); + removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.command('deployment-update-status-parameters') + .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.')) .option('--status', $('Remove the status value.')) @@ -5978,155 +5457,11 @@ exports.init = function (cli) { //update-status-by-deployment-name-parameters add deployment-update-status-parameters 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--key ', $('The JSON key.')) - .option('--value ', $('The JSON value.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Add the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'add'; - options.path = '' + '/' + options.key; - cli.output.verbose('options.path = ' + options.path); - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - var paramPath = '' + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //update-status-by-deployment-name-parameters set deployment-update-status-parameters - var catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = catparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.category('update-status-by-deployment-name-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - setparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Set the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //update-status-by-deployment-name-parameters remove deployment-update-status-parameters - 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--status', $('Remove the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'remove'; - options.path = ''; - var anySubItem = false || options.status; - if (anySubItem) { - var subItemPath = null; - if (options.status) { - subItemPath = options.path + '/status'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - } - else { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); - } - - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //update-status-by-deployment-name-parameters add deployment-update-status-parameters - 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.category('add') + .description($('Commands to add components of deployment in update-status-by-deployment-name-parameters file.')); + addparametersUpdateStatusByDeploymentNameDeploymentDeploymentUpdateStatusParameters2.command('deployment-update-status-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -6174,11 +5509,11 @@ exports.init = function (cli) { //update-status-by-deployment-name-parameters remove status 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentNameDeploymentStatus1 = parametersUpdateStatusByDeploymentNameDeploymentStatus1.category('status') - .description($('Commands to set/remove/add status of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpdateStatusByDeploymentNameDeploymentStatus1 = parametersUpdateStatusByDeploymentNameDeploymentStatus1.category('remove') + .description($('Commands to remove components of deployment in update-status-by-deployment-name-parameters file.')); + removeparametersUpdateStatusByDeploymentNameDeploymentStatus1.command('status') + .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.')) .execute(function(options, _) { @@ -6206,11 +5541,11 @@ exports.init = function (cli) { //update-status-by-deployment-name-parameters add status 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentNameDeploymentStatus2 = parametersUpdateStatusByDeploymentNameDeploymentStatus2.category('status') - .description($('Commands to set/remove/add status of deployment in update-status-by-deployment-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpdateStatusByDeploymentNameDeploymentStatus2 = parametersUpdateStatusByDeploymentNameDeploymentStatus2.category('add') + .description($('Commands to add components of deployment in update-status-by-deployment-name-parameters file.')); + addparametersUpdateStatusByDeploymentNameDeploymentStatus2.command('status') + .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.')) .option('--key ', $('The JSON key.')) @@ -6290,10 +5625,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.updateStatusByDeploymentSlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentUpdateStatusByDeploymentSlotupdateStatusByDeploymentSlotParameters2 = deploymentUpdateStatusByDeploymentSlot.category('update-status-by-deployment-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentUpdateStatusByDeploymentSlotupdateStatusByDeploymentSlotParameters2.command('generate') .description($('Generate deploymentUpdateStatusByDeploymentSlot parameter string or files.')) .usage('[options]') @@ -6355,206 +5692,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //update-status-by-deployment-slot-parameters set deployment-update-status-parameters - var catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.category('update-status-by-deployment-slot-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - setparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Set the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //update-status-by-deployment-slot-parameters remove deployment-update-status-parameters - 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--status', $('Remove the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'remove'; - options.path = ''; - var anySubItem = false || options.status; - if (anySubItem) { - var subItemPath = null; - if (options.status) { - subItemPath = options.path + '/status'; - jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); - } - } - else { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); - } - - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //update-status-by-deployment-slot-parameters add deployment-update-status-parameters - 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--key ', $('The JSON key.')) - .option('--value ', $('The JSON value.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Add the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'add'; - options.path = '' + '/' + options.key; - cli.output.verbose('options.path = ' + options.path); - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - var paramPath = '' + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //update-status-by-deployment-slot-parameters set deployment-update-status-parameters - var catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = catparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.category('update-status-by-deployment-slot-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - setparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--status ', $('Set the status value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = ''; - var paramPath = options.path + '/' + 'status'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.status) { - if (options.parse && options.status) { - options.status = JSON.parse(options.status); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.status}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //update-status-by-deployment-slot-parameters remove deployment-update-status-parameters 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.category('remove') + .description($('Commands to remove components of deployment in update-status-by-deployment-slot-parameters file.')); + removeparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters1.command('deployment-update-status-parameters') + .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.')) .option('--status', $('Remove the status value.')) @@ -6594,11 +5739,11 @@ exports.init = function (cli) { //update-status-by-deployment-slot-parameters add deployment-update-status-parameters 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('deployment-update-status-parameters') - .description($('Commands to set/remove/add deployment-update-status-parameters of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2 = parametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.category('add') + .description($('Commands to add components of deployment in update-status-by-deployment-slot-parameters file.')); + addparametersUpdateStatusByDeploymentSlotDeploymentDeploymentUpdateStatusParameters2.command('deployment-update-status-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -6646,11 +5791,11 @@ exports.init = function (cli) { //update-status-by-deployment-slot-parameters remove status 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 parameter for your deployment.')); - var removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1 = parametersUpdateStatusByDeploymentSlotDeploymentStatus1.category('status') - .description($('Commands to set/remove/add status of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1 = parametersUpdateStatusByDeploymentSlotDeploymentStatus1.category('remove') + .description($('Commands to remove components of deployment in update-status-by-deployment-slot-parameters file.')); + removeparametersUpdateStatusByDeploymentSlotDeploymentStatus1.command('status') + .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.')) .execute(function(options, _) { @@ -6678,11 +5823,11 @@ exports.init = function (cli) { //update-status-by-deployment-slot-parameters add status 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 the parameter input file for your deployment.')); - var addparametersUpdateStatusByDeploymentSlotDeploymentStatus2 = parametersUpdateStatusByDeploymentSlotDeploymentStatus2.category('status') - .description($('Commands to set/remove/add status of deployment in update-status-by-deployment-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpdateStatusByDeploymentSlotDeploymentStatus2 = parametersUpdateStatusByDeploymentSlotDeploymentStatus2.category('add') + .description($('Commands to add components of deployment in update-status-by-deployment-slot-parameters file.')); + addparametersUpdateStatusByDeploymentSlotDeploymentStatus2.command('status') + .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.')) .option('--key ', $('The JSON key.')) @@ -6788,10 +5933,12 @@ exports.init = function (cli) { var subscription = profile.current.getSubscription(options.subscription); var computeManagementClient = utils.createComputeClient(subscription); var result = computeManagementClient.deployment.upgradeByName(serviceName, deploymentName, parametersObj, _); - cli.output.json(result); + if (result) { + cli.output.json(result); + } }); var deploymentUpgradeByNameupgradeByNameParameters2 = deploymentUpgradeByName.category('upgrade-by-name-parameters') - .description($('Commands to generate parameter input file for your deployment.')); + .description($('Commands to manage configuration of deployment in the parameter file.')); deploymentUpgradeByNameupgradeByNameParameters2.command('generate') .description($('Generate deploymentUpgradeByName parameter string or files.')) .usage('[options]') @@ -6856,11 +6003,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters set deployment-upgrade-parameters 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('set') + .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); + setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.command('deployment-upgrade-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -6981,11 +6128,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters remove deployment-upgrade-parameters 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('remove') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.command('deployment-upgrade-parameters') + .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.')) .option('--configuration', $('Remove the configuration value.')) @@ -7060,11 +6207,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters add deployment-upgrade-parameters 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('add') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.command('deployment-upgrade-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -7186,73 +6333,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set extension-configuration - var catparametersUpgradeByNameDeploymentExtensionConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpgradeByNameDeploymentExtensionConfiguration0 = catparametersUpgradeByNameDeploymentExtensionConfiguration0.category('upgrade-by-name-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentExtensionConfiguration0 = parametersUpgradeByNameDeploymentExtensionConfiguration0.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentExtensionConfiguration0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--all-roles ', $('Set the all-roles value.')) - .option('--named-roles ', $('Set the named-roles value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/extensionConfiguration'; - var paramPath = options.path + '/' + 'allRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.allRoles) { - if (options.parse && options.allRoles) { - options.allRoles = JSON.parse(options.allRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.allRoles}]); - } - paramPath = options.path + '/' + 'namedRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.namedRoles) { - if (options.parse && options.namedRoles) { - options.namedRoles = JSON.parse(options.namedRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.namedRoles}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - //upgrade-by-name-parameters remove extension-configuration 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentExtensionConfiguration1 = parametersUpgradeByNameDeploymentExtensionConfiguration1.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpgradeByNameDeploymentExtensionConfiguration1 = parametersUpgradeByNameDeploymentExtensionConfiguration1.category('remove') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentExtensionConfiguration1.command('extension-configuration') + .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.')) .option('--all-roles', $('Remove the all-roles value.')) @@ -7297,11 +6385,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters add extension-configuration 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentExtensionConfiguration2 = parametersUpgradeByNameDeploymentExtensionConfiguration2.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpgradeByNameDeploymentExtensionConfiguration2 = parametersUpgradeByNameDeploymentExtensionConfiguration2.category('add') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentExtensionConfiguration2.command('extension-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -7360,11 +6448,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters set all-roles 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentAllRoles0 = parametersUpgradeByNameDeploymentAllRoles0.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersUpgradeByNameDeploymentAllRoles0 = parametersUpgradeByNameDeploymentAllRoles0.category('set') + .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); + setparametersUpgradeByNameDeploymentAllRoles0.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7424,11 +6512,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters remove all-roles 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentAllRoles1 = parametersUpgradeByNameDeploymentAllRoles1.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpgradeByNameDeploymentAllRoles1 = parametersUpgradeByNameDeploymentAllRoles1.category('remove') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentAllRoles1.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7474,11 +6562,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters add all-roles 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentAllRoles2 = parametersUpgradeByNameDeploymentAllRoles2.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpgradeByNameDeploymentAllRoles2 = parametersUpgradeByNameDeploymentAllRoles2.category('add') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentAllRoles2.command('all-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -7537,11 +6625,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters set named-roles 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentNamedRoles0 = parametersUpgradeByNameDeploymentNamedRoles0.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersUpgradeByNameDeploymentNamedRoles0 = parametersUpgradeByNameDeploymentNamedRoles0.category('set') + .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); + setparametersUpgradeByNameDeploymentNamedRoles0.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7601,11 +6689,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters remove named-roles 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentNamedRoles1 = parametersUpgradeByNameDeploymentNamedRoles1.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpgradeByNameDeploymentNamedRoles1 = parametersUpgradeByNameDeploymentNamedRoles1.category('remove') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentNamedRoles1.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7651,11 +6739,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters add named-roles 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentNamedRoles2 = parametersUpgradeByNameDeploymentNamedRoles2.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpgradeByNameDeploymentNamedRoles2 = parametersUpgradeByNameDeploymentNamedRoles2.category('add') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentNamedRoles2.command('named-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -7714,11 +6802,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters set extensions 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentExtensions0 = parametersUpgradeByNameDeploymentExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var setparametersUpgradeByNameDeploymentExtensions0 = parametersUpgradeByNameDeploymentExtensions0.category('set') + .description($('Commands to set components of deployment in upgrade-by-name-parameters file.')); + setparametersUpgradeByNameDeploymentExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7757,11 +6845,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters remove extensions 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentExtensions1 = parametersUpgradeByNameDeploymentExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var removeparametersUpgradeByNameDeploymentExtensions1 = parametersUpgradeByNameDeploymentExtensions1.category('remove') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -7792,11 +6880,11 @@ exports.init = function (cli) { //upgrade-by-name-parameters add extensions 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentExtensions2 = parametersUpgradeByNameDeploymentExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + .description($('Commands to manage configuration of deployment in the parameter file.')); + var addparametersUpgradeByNameDeploymentExtensions2 = parametersUpgradeByNameDeploymentExtensions2.category('add') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -7830,14 +6918,226 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set deployment-upgrade-parameters - 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentDeploymentUpgradeParameters0 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters0.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-name-parameters remove mode + 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') + .description($('Commands to remove components of deployment in upgrade-by-name-parameters file.')); + removeparametersUpgradeByNameDeploymentMode1.command('mode') + .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.')) + .execute(function(options, _) { + cli.output.verbose(JSON.stringify(options), _); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + options.operation = 'remove'; + options.path = '/mode'; + + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + //upgrade-by-name-parameters add mode + 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') + .description($('Commands to add components of deployment in upgrade-by-name-parameters file.')); + addparametersUpgradeByNameDeploymentMode2.command('mode') + .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.')) + .option('--key ', $('The JSON key.')) + .option('--value ', $('The JSON value.')) + .option('--parse', $('Parse the input value string to a JSON object.')) + .execute(function(options, _) { + cli.output.verbose(JSON.stringify(options), _); + if (options.parse && options.value) { + options.value = JSON.parse(options.value); + } + cli.output.verbose(options.value); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + options.operation = 'add'; + options.path = '/mode' + '/' + options.key; + cli.output.verbose('options.path = ' + options.path); + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + + +/* + Deployment UpgradeBySlot + --service-name + --deployment-slot + --parameters +============================================= +{ + "configuration":"", + "extendedProperties":{ + }, + "extensionConfiguration":{ + "allRoles":[ + { + "id":"", + "state":"" + } + ], + "namedRoles":[ + { + "extensions":[ + { + "id":"", + "state":"" + } + ], + "roleName":"" + } + ] + }, + "force":false, + "label":"", + "mode":0, + "packageUri":"", + "roleToUpgrade":"" +} +*/ + var deploymentUpgradeBySlot = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment') + .description($('Commands to manage your deployment. ')); + deploymentUpgradeBySlot.command('upgrade-by-slot [service-name] [deployment-slot] [parameters]') + .description($('The Upgrade Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)')) + .usage('[options] ') + .option('--service-name ', $('service-name')) + .option('--deployment-slot ', $('deployment-slot')) + .option('-p, --parameters ', $('parameters')) + .option('--parameter-file ', $('the input parameter file')) + .option('-s, --subscription ', $('the subscription identifier')) + .execute(function(serviceName, deploymentSlot, parameters, options, _) { + if (!serviceName) { + serviceName = cli.interaction.promptIfNotGiven($('service-name : '), serviceName, _) + } + + cli.output.verbose('serviceName = ' + serviceName); + if (!deploymentSlot) { + deploymentSlot = cli.interaction.promptIfNotGiven($('deployment-slot : '), deploymentSlot, _) + } + + cli.output.verbose('deploymentSlot = ' + deploymentSlot); + cli.output.verbose('parameters = ' + parameters); + var parametersObj = null; + if (options.parameterFile) { + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + parametersObj = JSON.parse(fileContent); + } + else { + parametersObj = JSON.parse(parameters); + } + cli.output.verbose('parametersObj = ' + JSON.stringify(parametersObj)); + var subscription = profile.current.getSubscription(options.subscription); + var computeManagementClient = utils.createComputeClient(subscription); + var result = computeManagementClient.deployment.upgradeBySlot(serviceName, deploymentSlot, parametersObj, _); + if (result) { + cli.output.json(result); + } + }); + var deploymentUpgradeBySlotupgradeBySlotParameters2 = deploymentUpgradeBySlot.category('upgrade-by-slot-parameters') + .description($('Commands to manage configuration of deployment in the parameter file.')); + deploymentUpgradeBySlotupgradeBySlotParameters2.command('generate') + .description($('Generate deploymentUpgradeBySlot parameter string or files.')) + .usage('[options]') + .option('--parameter-file ', $('The parameter file path.')) + .execute(function(options, _) { + cli.output.verbose('{\"configuration\":\"\",\"extendedProperties\":{},\"extensionConfiguration\":{\"allRoles\":[{\"id\":\"\",\"state\":\"\"}],\"namedRoles\":[{\"extensions\":[{\"id\":\"\",\"state\":\"\"}],\"roleName\":\"\"}]},\"force\":false,\"label\":\"\",\"mode\":0,\"packageUri\":\"\",\"roleToUpgrade\":\"\"}', _); + var filePath = 'deploymentUpgradeBySlot_upgradeBySlot.json'; + if (options.parameterFile) { + filePath = options.parameterFile; + } + fs.writeFileSync(filePath, beautify('{\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}')); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file output to: ' + filePath); + cli.output.verbose('====================================='); + }); + + deploymentUpgradeBySlotupgradeBySlotParameters2.command('patch') + .description($('Command to patch deploymentUpgradeBySlot parameter JSON file.')) + .usage('[options]') + .option('--parameter-file ', $('The parameter file path.')) + .option('--operation ', $('The JSON patch operation: add, remove, or replace.')) + .option('--path ', $('The JSON data path, e.g.: \"foo/1\".')) + .option('--value ', $('The JSON value.')) + .option('--parse', $('Parse the JSON value to object.')) + .execute(function(options, _) { + cli.output.verbose(options.parameterFile, _); + cli.output.verbose(options.operation); + cli.output.verbose(options.path); + cli.output.verbose(options.value); + cli.output.verbose(options.parse); + if (options.parse) { + options.value = JSON.parse(options.value); + } + cli.output.verbose(options.value); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + if (options.operation == 'add') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + } + else if (options.operation == 'remove') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); + } + else if (options.operation == 'replace') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + } + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + + //upgrade-by-slot-parameters set deployment-upgrade-parameters + 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') + .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); + setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.command('deployment-upgrade-parameters') + .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.')) .option('--parse', $('Parse the input value string to a JSON object.')) @@ -7955,14 +7255,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters remove deployment-upgrade-parameters - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentDeploymentUpgradeParameters1 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters1.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove deployment-upgrade-parameters + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters1.command('deployment-upgrade-parameters') + .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.')) .option('--configuration', $('Remove the configuration value.')) @@ -8034,14 +7334,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add deployment-upgrade-parameters - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentDeploymentUpgradeParameters2 = parametersUpgradeByNameDeploymentDeploymentUpgradeParameters2.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add deployment-upgrade-parameters + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters2.command('deployment-upgrade-parameters') + .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.')) .option('--key ', $('The JSON key.')) @@ -8163,73 +7463,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set extension-configuration - var catparametersUpgradeByNameDeploymentExtensionConfiguration0 = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment'); - var parametersUpgradeByNameDeploymentExtensionConfiguration0 = catparametersUpgradeByNameDeploymentExtensionConfiguration0.category('upgrade-by-name-parameters') - .description($('Commands to manage parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentExtensionConfiguration0 = parametersUpgradeByNameDeploymentExtensionConfiguration0.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - setparametersUpgradeByNameDeploymentExtensionConfiguration0.command('set') - .description($('Set 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--all-roles ', $('Set the all-roles value.')) - .option('--named-roles ', $('Set the named-roles value.')) - .execute(function(options, _) { - cli.output.verbose(JSON.stringify(options), _); - if (options.parse && options.value) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - options.operation = 'replace'; - options.path = '/extensionConfiguration'; - var paramPath = options.path + '/' + 'allRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.allRoles) { - if (options.parse && options.allRoles) { - options.allRoles = JSON.parse(options.allRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.allRoles}]); - } - paramPath = options.path + '/' + 'namedRoles'; - cli.output.verbose('================================================'); - cli.output.verbose('JSON Parameters Path:' + paramPath); - cli.output.verbose('================================================'); - if (options.namedRoles) { - if (options.parse && options.namedRoles) { - options.namedRoles = JSON.parse(options.namedRoles); - } - jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.namedRoles}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //upgrade-by-name-parameters remove extension-configuration - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentExtensionConfiguration1 = parametersUpgradeByNameDeploymentExtensionConfiguration1.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove extension-configuration + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentExtensionConfiguration1.command('extension-configuration') + .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.')) .option('--all-roles', $('Remove the all-roles value.')) @@ -8271,14 +7512,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add extension-configuration - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentExtensionConfiguration2 = parametersUpgradeByNameDeploymentExtensionConfiguration2.category('extension-configuration') - .description($('Commands to set/remove/add extension-configuration of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add extension-configuration + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentExtensionConfiguration2.command('extension-configuration') + .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.')) .option('--key ', $('The JSON key.')) @@ -8334,14 +7575,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set all-roles - 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentAllRoles0 = parametersUpgradeByNameDeploymentAllRoles0.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters set all-roles + 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') + .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); + setparametersUpgradeBySlotDeploymentAllRoles0.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8398,14 +7639,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters remove all-roles - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentAllRoles1 = parametersUpgradeByNameDeploymentAllRoles1.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove all-roles + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentAllRoles1.command('all-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8448,14 +7689,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add all-roles - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentAllRoles2 = parametersUpgradeByNameDeploymentAllRoles2.category('all-roles') - .description($('Commands to set/remove/add all-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add all-roles + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentAllRoles2.command('all-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -8511,14 +7752,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set named-roles - 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentNamedRoles0 = parametersUpgradeByNameDeploymentNamedRoles0.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters set named-roles + 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') + .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); + setparametersUpgradeBySlotDeploymentNamedRoles0.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8575,14 +7816,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters remove named-roles - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentNamedRoles1 = parametersUpgradeByNameDeploymentNamedRoles1.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove named-roles + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentNamedRoles1.command('named-roles') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8625,14 +7866,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add named-roles - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentNamedRoles2 = parametersUpgradeByNameDeploymentNamedRoles2.category('named-roles') - .description($('Commands to set/remove/add named-roles of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add named-roles + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentNamedRoles2.command('named-roles') + .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.')) .option('--key ', $('The JSON key.')) @@ -8688,14 +7929,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters set extensions - 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 parameter for your deployment.')); - var setparametersUpgradeByNameDeploymentExtensions0 = parametersUpgradeByNameDeploymentExtensions0.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters set extensions + 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') + .description($('Commands to set components of deployment in upgrade-by-slot-parameters file.')); + setparametersUpgradeBySlotDeploymentExtensions0.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8731,14 +7972,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters remove extensions - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentExtensions1 = parametersUpgradeByNameDeploymentExtensions1.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove extensions + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentExtensions1.command('extensions') + .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.')) .option('--index ', $('Indexer: index.')) @@ -8766,14 +8007,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add extensions - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentExtensions2 = parametersUpgradeByNameDeploymentExtensions2.category('extensions') - .description($('Commands to set/remove/add extensions of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add extensions + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentExtensions2.command('extensions') + .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.')) .option('--key ', $('The JSON key.')) @@ -8807,14 +8048,14 @@ exports.init = function (cli) { cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters remove mode - 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 parameter for your deployment.')); - var removeparametersUpgradeByNameDeploymentMode1 = parametersUpgradeByNameDeploymentMode1.category('mode') - .description($('Commands to set/remove/add mode of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters remove mode + 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') + .description($('Commands to remove components of deployment in upgrade-by-slot-parameters file.')); + removeparametersUpgradeBySlotDeploymentMode1.command('mode') + .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.')) .execute(function(options, _) { @@ -8839,14 +8080,14 @@ exports.init = function (cli) { cli.output.verbose('Parameter file updated at: ' + options.parameterFile); cli.output.verbose('====================================='); }); - //upgrade-by-name-parameters add mode - 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 the parameter input file for your deployment.')); - var addparametersUpgradeByNameDeploymentMode2 = parametersUpgradeByNameDeploymentMode2.category('mode') - .description($('Commands to set/remove/add mode of deployment in upgrade-by-name-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) + //upgrade-by-slot-parameters add mode + 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') + .description($('Commands to add components of deployment in upgrade-by-slot-parameters file.')); + addparametersUpgradeBySlotDeploymentMode2.command('mode') + .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.')) .option('--key ', $('The JSON key.')) @@ -8882,2438 +8123,276 @@ exports.init = function (cli) { /* - Deployment UpgradeBySlot + Deployment WalkUpgradeDomainByDeploymentName --service-name - --deployment-slot + --deployment-name --parameters ============================================= { - "configuration":"", - "extendedProperties":{ - }, - "extensionConfiguration":{ - "allRoles":[ - { - "id":"", - "state":"" + "upgradeDomain":0 +} +*/ + var deploymentWalkUpgradeDomainByDeploymentName = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment') + .description($('Commands to manage your deployment. ')); + deploymentWalkUpgradeDomainByDeploymentName.command('walk-upgrade-domain-by-deployment-name [service-name] [deployment-name] [parameters]') + .description($('The Walk Upgrade Domain By Deployment Name operation specifies an update domain in which a role instance must be updated. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the Management service has finished processing the request, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. Prior to calling the Walk Upgrade Domain operation you must have called Upgrade Deployment, Change Deployment Configuration, or Rollback Update Or Upgrade. By default, a service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To perform a manual update of your deployment, proceed in this order: Call Upgrade Deployment with the Mode element set to manual. Call Walk Upgrade Domain to update each domain within the deployment. Update domains must be updated in order. For example, begin with domain 0, proceed to domain 1, and so on. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. While an update is in progress, call Get Deployment to determine its status. If the update is in progress, Get Deployment returns an UpgradeStatus element that contains information about the update. If the update is complete, or if no update is in progress, then the UpgradeStatus element is null. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460800.aspx for more information)')) + .usage('[options] ') + .option('--service-name ', $('service-name')) + .option('--deployment-name ', $('deployment-name')) + .option('-p, --parameters ', $('parameters')) + .option('--parameter-file ', $('the input parameter file')) + .option('-s, --subscription ', $('the subscription identifier')) + .execute(function(serviceName, deploymentName, parameters, options, _) { + if (!serviceName) { + serviceName = cli.interaction.promptIfNotGiven($('service-name : '), serviceName, _) + } + + cli.output.verbose('serviceName = ' + serviceName); + if (!deploymentName) { + deploymentName = cli.interaction.promptIfNotGiven($('deployment-name : '), deploymentName, _) + } + + cli.output.verbose('deploymentName = ' + deploymentName); + cli.output.verbose('parameters = ' + parameters); + var parametersObj = null; + if (options.parameterFile) { + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + parametersObj = JSON.parse(fileContent); + } + else { + parametersObj = JSON.parse(parameters); + } + cli.output.verbose('parametersObj = ' + JSON.stringify(parametersObj)); + var subscription = profile.current.getSubscription(options.subscription); + var computeManagementClient = utils.createComputeClient(subscription); + var result = computeManagementClient.deployment.walkUpgradeDomainByDeploymentName(serviceName, deploymentName, parametersObj, _); + if (result) { + cli.output.json(result); + } + }); + var deploymentWalkUpgradeDomainByDeploymentNamewalkUpgradeDomainByDeploymentNameParameters2 = deploymentWalkUpgradeDomainByDeploymentName.category('walk-upgrade-domain-by-deployment-name-parameters') + .description($('Commands to manage configuration of deployment in the parameter file.')); + deploymentWalkUpgradeDomainByDeploymentNamewalkUpgradeDomainByDeploymentNameParameters2.command('generate') + .description($('Generate deploymentWalkUpgradeDomainByDeploymentName parameter string or files.')) + .usage('[options]') + .option('--parameter-file ', $('The parameter file path.')) + .execute(function(options, _) { + cli.output.verbose('{\"upgradeDomain\":0}', _); + var filePath = 'deploymentWalkUpgradeDomainByDeploymentName_walkUpgradeDomainByDeploymentName.json'; + if (options.parameterFile) { + filePath = options.parameterFile; + } + fs.writeFileSync(filePath, beautify('{\r\n\"upgradeDomain\":0\r\n}')); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file output to: ' + filePath); + cli.output.verbose('====================================='); + }); + + deploymentWalkUpgradeDomainByDeploymentNamewalkUpgradeDomainByDeploymentNameParameters2.command('patch') + .description($('Command to patch deploymentWalkUpgradeDomainByDeploymentName parameter JSON file.')) + .usage('[options]') + .option('--parameter-file ', $('The parameter file path.')) + .option('--operation ', $('The JSON patch operation: add, remove, or replace.')) + .option('--path ', $('The JSON data path, e.g.: \"foo/1\".')) + .option('--value ', $('The JSON value.')) + .option('--parse', $('Parse the JSON value to object.')) + .execute(function(options, _) { + cli.output.verbose(options.parameterFile, _); + cli.output.verbose(options.operation); + cli.output.verbose(options.path); + cli.output.verbose(options.value); + cli.output.verbose(options.parse); + if (options.parse) { + options.value = JSON.parse(options.value); + } + cli.output.verbose(options.value); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + if (options.operation == 'add') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + } + else if (options.operation == 'remove') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); + } + else if (options.operation == 'replace') { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + } + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + + //walk-upgrade-domain-by-deployment-name-parameters set deployment-walk-upgrade-domain-parameters + 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') + .description($('Commands to set components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); + setparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters0.command('deployment-walk-upgrade-domain-parameters') + .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.')) + .option('--parse', $('Parse the input value string to a JSON object.')) + .option('--upgrade-domain ', $('Set the upgrade-domain value.')) + .execute(function(options, _) { + cli.output.verbose(JSON.stringify(options), _); + if (options.parse && options.value) { + options.value = JSON.parse(options.value); + } + cli.output.verbose(options.value); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + options.operation = 'replace'; + options.path = ''; + var paramPath = options.path + '/' + 'upgradeDomain'; + cli.output.verbose('================================================'); + cli.output.verbose('JSON Parameters Path:' + paramPath); + cli.output.verbose('================================================'); + if (options.upgradeDomain) { + if (options.parse && options.upgradeDomain) { + options.upgradeDomain = JSON.parse(options.upgradeDomain); } - ], - "namedRoles":[ - { - "extensions":[ - { - "id":"", - "state":"" - } - ], - "roleName":"" + jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.upgradeDomain}]); + } + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + + //walk-upgrade-domain-by-deployment-name-parameters remove deployment-walk-upgrade-domain-parameters + 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') + .description($('Commands to remove components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); + removeparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters1.command('deployment-walk-upgrade-domain-parameters') + .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.')) + .option('--upgrade-domain', $('Remove the upgrade-domain value.')) + .execute(function(options, _) { + cli.output.verbose(JSON.stringify(options), _); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + options.operation = 'remove'; + options.path = ''; + var anySubItem = false || options.upgradeDomain; + if (anySubItem) { + var subItemPath = null; + if (options.upgradeDomain) { + subItemPath = options.path + '/upgradeDomain'; + jsonpatch.apply(parametersObj, [{op: options.operation, path: subItemPath}]); } - ] - }, - "force":false, - "label":"", - "mode":0, - "packageUri":"", - "roleToUpgrade":"" + } + else { + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); + } + + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + //walk-upgrade-domain-by-deployment-name-parameters add deployment-walk-upgrade-domain-parameters + 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') + .description($('Commands to add components of deployment in walk-upgrade-domain-by-deployment-name-parameters file.')); + addparametersWalkUpgradeDomainByDeploymentNameDeploymentDeploymentWalkUpgradeDomainParameters2.command('deployment-walk-upgrade-domain-parameters') + .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.')) + .option('--key ', $('The JSON key.')) + .option('--value ', $('The JSON value.')) + .option('--parse', $('Parse the input value string to a JSON object.')) + .option('--upgrade-domain ', $('Add the upgrade-domain value.')) + .execute(function(options, _) { + cli.output.verbose(JSON.stringify(options), _); + if (options.parse && options.value) { + options.value = JSON.parse(options.value); + } + cli.output.verbose(options.value); + cli.output.verbose('====================================='); + cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); + cli.output.verbose('====================================='); + var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); + var parametersObj = JSON.parse(fileContent); + cli.output.verbose('JSON object:'); + cli.output.verbose(JSON.stringify(parametersObj)); + options.operation = 'add'; + options.path = '' + '/' + options.key; + cli.output.verbose('options.path = ' + options.path); + jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); + var paramPath = '' + '/' + 'upgradeDomain'; + cli.output.verbose('================================================'); + cli.output.verbose('JSON Parameters Path:' + paramPath); + cli.output.verbose('================================================'); + if (options.upgradeDomain) { + if (options.parse && options.upgradeDomain) { + options.upgradeDomain = JSON.parse(options.upgradeDomain); + } + jsonpatch.apply(parametersObj, [{op: options.operation, path: paramPath, value: options.upgradeDomain}]); + } + var updatedContent = JSON.stringify(parametersObj); + cli.output.verbose('====================================='); + cli.output.verbose('JSON object (updated):'); + cli.output.verbose(JSON.stringify(parametersObj)); + cli.output.verbose('====================================='); + fs.writeFileSync(options.parameterFile, beautify(updatedContent)); + cli.output.verbose('====================================='); + cli.output.verbose('Parameter file updated at: ' + options.parameterFile); + cli.output.verbose('====================================='); + }); + + +/* + Deployment WalkUpgradeDomainByDeploymentSlot + --service-name + --deployment-slot + --parameters +============================================= +{ + "upgradeDomain":0 } */ - var deploymentUpgradeBySlot = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment') + var deploymentWalkUpgradeDomainByDeploymentSlot = cli.category('invoke').description('Commands to invoke service management operations.').category('deployment') .description($('Commands to manage your deployment. ')); - deploymentUpgradeBySlot.command('upgrade-by-slot [service-name] [deployment-slot] [parameters]') - .description($('The Upgrade Deployment By Slot operation initiates an update of role instances in a deployment using the package and configuration that you specify. For more information about updating role instances, see Update an Azure Service at http://msdn.microsoft.com/en-us/library/windowsazure/hh472157.aspx. This operation is an asynchronous operation. To determine whether the request has been processed, call Get Operation Status. For more information on asynchronous operations, see Tracking Asynchronous Service Management Requests at http://msdn.microsoft.com/en-us/library/windowsazure/ee460791.aspx. To perform an automatic update of a deployment, call Upgrade Deployment or Change Deployment Configuration with the Mode element set to automatic. The update proceeds from that point without a need for further input. You can call Get Operation Status to determine when the update is complete. To perform a manual update, first call Upgrade Deployment with the Mode element set to manual. Next, call Walk Upgrade Domain to update each domain within the deployment. You should make sure that the operation is complete by calling Get Operation Status before updating the next domain. Important: An update that adds or removes role instances will result in a configuration update to all roles that are deployed in the cloud service. Existing role instances need to be notified of new role instances so that all role instances can communicate together in the cloud service. By default, a cloud service is deployed with five update domains, which are updated one at a time during an in-place update. For information on modifying the number of update domains in the service definition file, see the Azure Service Definition Schema (.csdef File). To determine the update domain in which a particular instance is running in Windows Azure, use the UpdateDomain property of the RoleInstance class. See the Azure Managed Library Reference at http://msdn.microsoft.com/en-us/library/windowsazure/dd179380.aspx for more information. (see http://msdn.microsoft.com/en-us/library/windowsazure/ee460793.aspx for more information)')) - .usage('[options] ') - .option('--service-name ', $('service-name')) - .option('--deployment-slot ', $('deployment-slot')) - .option('-p, --parameters ', $('parameters')) - .option('--parameter-file ', $('the input parameter file')) - .option('-s, --subscription ', $('the subscription identifier')) - .execute(function(serviceName, deploymentSlot, parameters, options, _) { - if (!serviceName) { - serviceName = cli.interaction.promptIfNotGiven($('service-name : '), serviceName, _) - } - - cli.output.verbose('serviceName = ' + serviceName); - if (!deploymentSlot) { - deploymentSlot = cli.interaction.promptIfNotGiven($('deployment-slot : '), deploymentSlot, _) - } - - cli.output.verbose('deploymentSlot = ' + deploymentSlot); - cli.output.verbose('parameters = ' + parameters); - var parametersObj = null; - if (options.parameterFile) { - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - parametersObj = JSON.parse(fileContent); - } - else { - parametersObj = JSON.parse(parameters); - } - cli.output.verbose('parametersObj = ' + JSON.stringify(parametersObj)); - var subscription = profile.current.getSubscription(options.subscription); - var computeManagementClient = utils.createComputeClient(subscription); - var result = computeManagementClient.deployment.upgradeBySlot(serviceName, deploymentSlot, parametersObj, _); - cli.output.json(result); - }); - var deploymentUpgradeBySlotupgradeBySlotParameters2 = deploymentUpgradeBySlot.category('upgrade-by-slot-parameters') - .description($('Commands to generate parameter input file for your deployment.')); - deploymentUpgradeBySlotupgradeBySlotParameters2.command('generate') - .description($('Generate deploymentUpgradeBySlot parameter string or files.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .execute(function(options, _) { - cli.output.verbose('{\"configuration\":\"\",\"extendedProperties\":{},\"extensionConfiguration\":{\"allRoles\":[{\"id\":\"\",\"state\":\"\"}],\"namedRoles\":[{\"extensions\":[{\"id\":\"\",\"state\":\"\"}],\"roleName\":\"\"}]},\"force\":false,\"label\":\"\",\"mode\":0,\"packageUri\":\"\",\"roleToUpgrade\":\"\"}', _); - var filePath = 'deploymentUpgradeBySlot_upgradeBySlot.json'; - if (options.parameterFile) { - filePath = options.parameterFile; - } - fs.writeFileSync(filePath, beautify('{\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}')); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file output to: ' + filePath); - cli.output.verbose('====================================='); - }); - - deploymentUpgradeBySlotupgradeBySlotParameters2.command('patch') - .description($('Command to patch deploymentUpgradeBySlot parameter JSON file.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--operation ', $('The JSON patch operation: add, remove, or replace.')) - .option('--path ', $('The JSON data path, e.g.: \"foo/1\".')) - .option('--value ', $('The JSON value.')) - .option('--parse', $('Parse the JSON value to object.')) - .execute(function(options, _) { - cli.output.verbose(options.parameterFile, _); - cli.output.verbose(options.operation); - cli.output.verbose(options.path); - cli.output.verbose(options.value); - cli.output.verbose(options.parse); - if (options.parse) { - options.value = JSON.parse(options.value); - } - cli.output.verbose(options.value); - cli.output.verbose('====================================='); - cli.output.verbose('Reading file content from: \"' + options.parameterFile + '\"'); - cli.output.verbose('====================================='); - var fileContent = fs.readFileSync(options.parameterFile, 'utf8'); - var parametersObj = JSON.parse(fileContent); - cli.output.verbose('JSON object:'); - cli.output.verbose(JSON.stringify(parametersObj)); - if (options.operation == 'add') { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - } - else if (options.operation == 'remove') { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path}]); - } - else if (options.operation == 'replace') { - jsonpatch.apply(parametersObj, [{op: options.operation, path: options.path, value: options.value}]); - } - var updatedContent = JSON.stringify(parametersObj); - cli.output.verbose('====================================='); - cli.output.verbose('JSON object (updated):'); - cli.output.verbose(JSON.stringify(parametersObj)); - cli.output.verbose('====================================='); - fs.writeFileSync(options.parameterFile, beautify(updatedContent)); - cli.output.verbose('====================================='); - cli.output.verbose('Parameter file updated at: ' + options.parameterFile); - cli.output.verbose('====================================='); - }); - - //upgrade-by-slot-parameters set deployment-upgrade-parameters - 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 parameter for your deployment.')); - var setparametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0 = parametersUpgradeBySlotDeploymentDeploymentUpgradeParameters0.category('deployment-upgrade-parameters') - .description($('Commands to set/remove/add deployment-upgrade-parameters of deployment in upgrade-by-slot-parameters file.')); - 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 create-or-update-parameters * generate/set/remove/add\' commands \r\n are used to configure the input parameter file. The \'vmss create-or-update\' command takes a parameter \r\n file as for the VM scale set configuration, and creates it online.')) - .usage('[options]') - .option('--parameter-file ', $('The parameter file path.')) - .option('--parse', $('Parse the input value string to a JSON object.')) - .option('--configuration ', $('Set the configuration value.')) - .option('--extended-properties ', $('Set the extended-properties value.')) - .option('--extension-configuration ', $('Set the extension-configuration value.')) - .option('--force ', $('Set the force value.')) - .option('--label - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement.Test/packages.config b/src/ServiceManagement/Compute/Commands.ServiceManagement.Test/packages.config index ac0dfd76322a..49198e94b83a 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement.Test/packages.config +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement.Test/packages.config @@ -22,7 +22,7 @@ - + diff --git a/src/ServiceManagement/Compute/Commands.ServiceManagement/Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.psd1 b/src/ServiceManagement/Compute/Commands.ServiceManagement/Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.psd1 index e7af7051e410..4bc3dc4e06ee 100644 --- a/src/ServiceManagement/Compute/Commands.ServiceManagement/Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.psd1 +++ b/src/ServiceManagement/Compute/Commands.ServiceManagement/Microsoft.WindowsAzure.Commands.ServiceManagement.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/ExpressRoute.psd1 b/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/ExpressRoute.psd1 index 5216c51d8d8a..7613ab72db0e 100644 --- a/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/ExpressRoute.psd1 +++ b/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/ExpressRoute.psd1 @@ -87,7 +87,28 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/Microsoft.WindowsAzure.Commands.ExpressRoute.dll-help.psd1 b/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/Microsoft.WindowsAzure.Commands.ExpressRoute.dll-help.psd1 index 29d5a1f362ae..15317f02fda9 100644 --- a/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/Microsoft.WindowsAzure.Commands.ExpressRoute.dll-help.psd1 +++ b/src/ServiceManagement/ExpressRoute/Commands.ExpressRoute/Microsoft.WindowsAzure.Commands.ExpressRoute.dll-help.psd1 @@ -87,7 +87,28 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj b/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj index 256558538b2a..a2f0c0c8ebd5 100644 --- a/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj +++ b/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/Commands.HDInsight.Test.csproj @@ -144,7 +144,7 @@ True - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll diff --git a/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/packages.config b/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/packages.config index a97376b14be6..37715c6aed0e 100644 --- a/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/packages.config +++ b/src/ServiceManagement/HDInsight/Commands.HDInsight.Test/packages.config @@ -21,7 +21,7 @@ - + diff --git a/src/ServiceManagement/HDInsight/Commands.HDInsight/Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.psd1 b/src/ServiceManagement/HDInsight/Commands.HDInsight/Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.psd1 index 9e63ca361531..7a2d217bfef2 100644 --- a/src/ServiceManagement/HDInsight/Commands.HDInsight/Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.psd1 +++ b/src/ServiceManagement/HDInsight/Commands.HDInsight/Microsoft.WindowsAzure.Commands.HDInsight.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/Commands.ManagedCache.Test.csproj b/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/Commands.ManagedCache.Test.csproj index 225d4fa75645..08854be406ca 100644 --- a/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/Commands.ManagedCache.Test.csproj +++ b/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/Commands.ManagedCache.Test.csproj @@ -101,9 +101,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.4.1.1\lib\net40\Microsoft.WindowsAzure.Management.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/packages.config b/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/packages.config index a9d5da6e24a2..f5493f3401bd 100644 --- a/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/packages.config +++ b/src/ServiceManagement/ManagedCache/Commands.ManagedCache.Test/packages.config @@ -17,7 +17,7 @@ - + diff --git a/src/ServiceManagement/ManagedCache/Commands.ManagedCache/Microsoft.Azure.Commands.ManagedCache.dll-help.psd1 b/src/ServiceManagement/ManagedCache/Commands.ManagedCache/Microsoft.Azure.Commands.ManagedCache.dll-help.psd1 index 3aafca768a00..03c7520ef990 100644 --- a/src/ServiceManagement/ManagedCache/Commands.ManagedCache/Microsoft.Azure.Commands.ManagedCache.dll-help.psd1 +++ b/src/ServiceManagement/ManagedCache/Commands.ManagedCache/Microsoft.Azure.Commands.ManagedCache.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Network/Commands.Network.Test/Commands.ServiceManagement.Network.Test.csproj b/src/ServiceManagement/Network/Commands.Network.Test/Commands.ServiceManagement.Network.Test.csproj index 16dda156f7da..8201cb85b492 100644 --- a/src/ServiceManagement/Network/Commands.Network.Test/Commands.ServiceManagement.Network.Test.csproj +++ b/src/ServiceManagement/Network/Commands.Network.Test/Commands.ServiceManagement.Network.Test.csproj @@ -112,9 +112,9 @@ False ..\..\..\packages\Microsoft.WindowsAzure.Management.Storage.5.1.1\lib\net40\Microsoft.WindowsAzure.Management.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/Network/Commands.Network.Test/packages.config b/src/ServiceManagement/Network/Commands.Network.Test/packages.config index 22f85440da76..5e6b01b2d5a9 100644 --- a/src/ServiceManagement/Network/Commands.Network.Test/packages.config +++ b/src/ServiceManagement/Network/Commands.Network.Test/packages.config @@ -20,7 +20,7 @@ - + diff --git a/src/ServiceManagement/Profile/Commands.Profile/Microsoft.WindowsAzure.Commands.Profile.dll-Help.psd1 b/src/ServiceManagement/Profile/Commands.Profile/Microsoft.WindowsAzure.Commands.Profile.dll-Help.psd1 index 0e82e959e647..176c995a5be6 100644 --- a/src/ServiceManagement/Profile/Commands.Profile/Microsoft.WindowsAzure.Commands.Profile.dll-Help.psd1 +++ b/src/ServiceManagement/Profile/Commands.Profile/Microsoft.WindowsAzure.Commands.Profile.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Profile/Commands.Profile/Subscription/SetAzureSubscription.cs b/src/ServiceManagement/Profile/Commands.Profile/Subscription/SetAzureSubscription.cs index 9c8ba0551dcb..09e76059dcb5 100644 --- a/src/ServiceManagement/Profile/Commands.Profile/Subscription/SetAzureSubscription.cs +++ b/src/ServiceManagement/Profile/Commands.Profile/Subscription/SetAzureSubscription.cs @@ -164,7 +164,7 @@ public override void ExecuteCmdlet() if (Profile.Context != null && Profile.Context.Subscription != null && Profile.Context.Subscription.Id == subscription.Id) { - ServiceManagementUtilities.ClearCurrentStorageAccount(); + GeneralUtilities.ClearCurrentStorageAccount(); } var context = new AzureContext(subscription, ProfileClient.GetAccount(subscription.Account), ProfileClient.GetEnvironmentOrDefault(subscription.Environment)); if (Context != null) diff --git a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.ScenarioTest/Commands.RemoteAppScenarioTest.csproj b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.ScenarioTest/Commands.RemoteAppScenarioTest.csproj index f82d61a91c65..9e9c75489d3e 100644 --- a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.ScenarioTest/Commands.RemoteAppScenarioTest.csproj +++ b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.ScenarioTest/Commands.RemoteAppScenarioTest.csproj @@ -85,8 +85,8 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.RemoteApp.2.0.4\lib\net40\Microsoft.WindowsAzure.Management.RemoteApp.dll - - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/Commands.RemoteApp.Test.csproj b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/Commands.RemoteApp.Test.csproj index 2b078724a4d9..fc0326ce7469 100644 --- a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/Commands.RemoteApp.Test.csproj +++ b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/Commands.RemoteApp.Test.csproj @@ -149,8 +149,8 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.RemoteApp.2.0.4\lib\net40\Microsoft.WindowsAzure.Management.RemoteApp.dll - - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/packages.config b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/packages.config index c55828853457..821b102885e2 100644 --- a/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/packages.config +++ b/src/ServiceManagement/RemoteApp/Commands.RemoteApp.Test/packages.config @@ -13,7 +13,7 @@ - + diff --git a/src/ServiceManagement/Services/Commands.Test.Utilities/Commands.Test.Utilities.csproj b/src/ServiceManagement/Services/Commands.Test.Utilities/Commands.Test.Utilities.csproj index 7a0efe146584..294a8362e8aa 100644 --- a/src/ServiceManagement/Services/Commands.Test.Utilities/Commands.Test.Utilities.csproj +++ b/src/ServiceManagement/Services/Commands.Test.Utilities/Commands.Test.Utilities.csproj @@ -97,9 +97,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.Storage.5.1.1\lib\net40\Microsoft.WindowsAzure.Management.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/Services/Commands.Test.Utilities/packages.config b/src/ServiceManagement/Services/Commands.Test.Utilities/packages.config index de7bc8b8d387..16655902e3a6 100644 --- a/src/ServiceManagement/Services/Commands.Test.Utilities/packages.config +++ b/src/ServiceManagement/Services/Commands.Test.Utilities/packages.config @@ -14,7 +14,7 @@ - + diff --git a/src/ServiceManagement/Services/Commands.Test/Commands.Test.csproj b/src/ServiceManagement/Services/Commands.Test/Commands.Test.csproj index a7f7827a8d8b..7293aa732894 100644 --- a/src/ServiceManagement/Services/Commands.Test/Commands.Test.csproj +++ b/src/ServiceManagement/Services/Commands.Test/Commands.Test.csproj @@ -160,9 +160,9 @@ False ..\..\..\packages\WindowsAzure.Storage.6.1.0\lib\net40\Microsoft.WindowsAzure.Storage.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll ..\..\..\packages\Newtonsoft.Json.6.0.8\lib\net45\Newtonsoft.Json.dll @@ -385,6 +385,9 @@ + + PreserveNewest + PreserveNewest @@ -412,6 +415,9 @@ Always + + PreserveNewest + diff --git a/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureProfileTests.cs b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureProfileTests.cs index c0f3c0d9d9a2..45f960767fe2 100644 --- a/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureProfileTests.cs +++ b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureProfileTests.cs @@ -27,7 +27,6 @@ public void TestSelectDefaultProfile() [Fact(Skip = "PSGet Migration: TODO Move to ARM")] [Trait(Category.AcceptanceType, Category.CheckIn)] - [Trait(Category.AcceptanceType, Category.CheckIn)] public void TestMakeArmCallWithCreatedProfile() { ProfileTestController.NewARMInstance.RunPSTestWithToken((context, token) => string.Format("Test-NewAzureProfileInARMMode {0} {1} {2}", token, context.Account.Id, context.Subscription.Id)); @@ -35,7 +34,6 @@ public void TestMakeArmCallWithCreatedProfile() [Fact] [Trait(Category.AcceptanceType, Category.CheckIn)] - [Trait(Category.AcceptanceType, Category.CheckIn)] public void TestMakeRdfeCallWithCreatedProfile() { ProfileTestController.NewRdfeInstance.RunPSTestWithToken((context, token) => string.Format("Test-NewAzureProfileInRDFEMode {0} {1} {2}", token, context.Account.Id, context.Subscription.Id)); diff --git a/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.cs b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.cs index c461714c25fe..5732aa3fcbf0 100644 --- a/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.cs +++ b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.cs @@ -17,8 +17,9 @@ using Xunit; using Microsoft.WindowsAzure.Commands.Profile; using Moq; +using Microsoft.Azure.Commands.Test.Profile; -namespace Microsoft.WindowsAzure.Commands.Test.Profile +namespace Microsoft.Azure.Commands.Test.Profile { public class SelectAzureSubscriptionTests @@ -43,5 +44,12 @@ public void CleansDefaultSubscriptionTwice() // Assert that no exception is thrown Assert.True(true); } + + [Fact] + [Trait(Category.AcceptanceType, Category.CheckIn)] + public void StorageAccountIsNotCleaned() + { + ProfileTestController.NewRdfeInstance.RunPsTest("Test-StorageAccountIsNotCleaned"); + } } } \ No newline at end of file diff --git a/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.ps1 b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.ps1 new file mode 100644 index 000000000000..fb7366f977aa --- /dev/null +++ b/src/ServiceManagement/Services/Commands.Test/Profile/SelectAzureSubscriptionTests.ps1 @@ -0,0 +1,25 @@ +# ---------------------------------------------------------------------------------- +# +# 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. +# ---------------------------------------------------------------------------------- + +<# +.SYNOPSIS +Tests creating new azure profile with access token +#> +function Test-StorageAccountIsNotCleaned +{ + Set-AzureSubscription -SubscriptionId 2c224e7e-3ef5-431d-a57b-e71f4662e3a6 -CurrentStorageAccount teststorage1220 + Select-AzureSubscription -SubscriptionId 2c224e7e-3ef5-431d-a57b-e71f4662e3a6 + $subscription = Get-AzureSubscription -SubscriptionId 2c224e7e-3ef5-431d-a57b-e71f4662e3a6 + Assert-NotNull $($subscription.CurrentStorageAccountName) +} diff --git a/src/ServiceManagement/Services/Commands.Test/SessionRecords/Microsoft.Azure.Commands.Test.Profile.SelectAzureSubscriptionTests/StorageAccountIsNotCleaned.json b/src/ServiceManagement/Services/Commands.Test/SessionRecords/Microsoft.Azure.Commands.Test.Profile.SelectAzureSubscriptionTests/StorageAccountIsNotCleaned.json new file mode 100644 index 000000000000..6500bd97b2bf --- /dev/null +++ b/src/ServiceManagement/Services/Commands.Test/SessionRecords/Microsoft.Azure.Commands.Test.Profile.SelectAzureSubscriptionTests/StorageAccountIsNotCleaned.json @@ -0,0 +1,90 @@ +{ + "Entries": [ + { + "RequestUri": "/2c224e7e-3ef5-431d-a57b-e71f4662e3a6/services/storageservices/teststorage1220", + "EncodedRequestUri": "LzJjMjI0ZTdlLTNlZjUtNDMxZC1hNTdiLWU3MWY0NjYyZTNhNi9zZXJ2aWNlcy9zdG9yYWdlc2VydmljZXMvdGVzdHN0b3JhZ2UxMjIw", + "RequestMethod": "GET", + "RequestBody": "", + "RequestHeaders": { + "x-ms-version": [ + "2014-10-01" + ], + "User-Agent": [ + "Microsoft.WindowsAzure.Management.Storage.StorageManagementClient/5.0.0.0" + ] + }, + "ResponseBody": "\r\n https://management.core.windows.net/2c224e7e-3ef5-431d-a57b-e71f4662e3a6/services/storageservices/teststorage1220\r\n teststorage1220\r\n \r\n \r\n West US\r\n \r\n Created\r\n \r\n https://teststorage1220.blob.core.windows.net/\r\n https://teststorage1220.queue.core.windows.net/\r\n https://teststorage1220.table.core.windows.net/\r\n https://teststorage1220.file.core.windows.net/\r\n \r\n West US\r\n Available\r\n \r\n \r\n 2014-07-09T19:35:26Z\r\n \r\n Standard_LRS\r\n \r\n \r\n \r\n ResourceGroup\r\n Default-Storage-WestUS\r\n \r\n \r\n ResourceLocation\r\n West US\r\n \r\n \r\n \r\n PersistentVMRole\r\n \r\n", + "ResponseHeaders": { + "Content-Length": [ + "1293" + ], + "Content-Type": [ + "application/xml; charset=utf-8" + ], + "x-ms-servedbyregion": [ + "ussouth3" + ], + "x-ms-request-id": [ + "3cc3414cd2838856bdfbece82a8a9ee5" + ], + "Cache-Control": [ + "no-cache" + ], + "Date": [ + "Mon, 07 Mar 2016 22:17:48 GMT" + ], + "Server": [ + "1.0.6198.323", + "(rd_rdfe_stable.160224-0707)", + "Microsoft-HTTPAPI/2.0" + ] + }, + "StatusCode": 200 + }, + { + "RequestUri": "/2c224e7e-3ef5-431d-a57b-e71f4662e3a6/services/storageservices/teststorage1220/keys", + "EncodedRequestUri": "LzJjMjI0ZTdlLTNlZjUtNDMxZC1hNTdiLWU3MWY0NjYyZTNhNi9zZXJ2aWNlcy9zdG9yYWdlc2VydmljZXMvdGVzdHN0b3JhZ2UxMjIwL2tleXM=", + "RequestMethod": "GET", + "RequestBody": "", + "RequestHeaders": { + "x-ms-version": [ + "2014-10-01" + ], + "User-Agent": [ + "Microsoft.WindowsAzure.Management.Storage.StorageManagementClient/5.0.0.0" + ] + }, + "ResponseBody": "\r\n https://management.core.windows.net/2c224e7e-3ef5-431d-a57b-e71f4662e3a6/services/storageservices/teststorage1220\r\n \r\n /hYt36JRM3StLgfEuTa4IOi9yWzKhBKhRY3V3WZjq97Fv/84wToozLuT0aVqioUtreSTBJMD+LXI4g5jI5MGWA==\r\n R1oLky011b/RZa9K6qVWKpnSsLjHMqvupJfg+DsbAZJxi1nN6Toc9ZNUQjMskDxQkdHaXmYY00jVxr86v4QPww==\r\n \r\n", + "ResponseHeaders": { + "Content-Length": [ + "518" + ], + "Content-Type": [ + "application/xml; charset=utf-8" + ], + "x-ms-servedbyregion": [ + "ussouth3" + ], + "x-ms-request-id": [ + "97717179d40c8f788e741e3cbe0e4b55" + ], + "Cache-Control": [ + "no-cache" + ], + "Date": [ + "Mon, 07 Mar 2016 22:17:48 GMT" + ], + "Server": [ + "1.0.6198.323", + "(rd_rdfe_stable.160224-0707)", + "Microsoft-HTTPAPI/2.0" + ] + }, + "StatusCode": 200 + } + ], + "Names": {}, + "Variables": { + "SubscriptionId": "2c224e7e-3ef5-431d-a57b-e71f4662e3a6" + } +} \ No newline at end of file diff --git a/src/ServiceManagement/Services/Commands.Test/packages.config b/src/ServiceManagement/Services/Commands.Test/packages.config index d02f7f2ac42b..367d36dd3475 100644 --- a/src/ServiceManagement/Services/Commands.Test/packages.config +++ b/src/ServiceManagement/Services/Commands.Test/packages.config @@ -27,7 +27,7 @@ - + diff --git a/src/ServiceManagement/Services/Commands.Utilities/Azure.psd1 b/src/ServiceManagement/Services/Commands.Utilities/Azure.psd1 index 010195c3b936..3125322d7948 100644 --- a/src/ServiceManagement/Services/Commands.Utilities/Azure.psd1 +++ b/src/ServiceManagement/Services/Commands.Utilities/Azure.psd1 @@ -215,6 +215,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/Sql/Commands.SqlDatabase/Microsoft.WindowsAzure.Commands.SqlDatabase.dll-Help.psd1 b/src/ServiceManagement/Sql/Commands.SqlDatabase/Microsoft.WindowsAzure.Commands.SqlDatabase.dll-Help.psd1 index df4b2f8ce47d..97ee8ab16654 100644 --- a/src/ServiceManagement/Sql/Commands.SqlDatabase/Microsoft.WindowsAzure.Commands.SqlDatabase.dll-Help.psd1 +++ b/src/ServiceManagement/Sql/Commands.SqlDatabase/Microsoft.WindowsAzure.Commands.SqlDatabase.dll-Help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/StorSimple/Commands.StorSimple/Microsoft.WindowsAzure.Commands.StorSimple.dll-help.psd1 b/src/ServiceManagement/StorSimple/Commands.StorSimple/Microsoft.WindowsAzure.Commands.StorSimple.dll-help.psd1 index 69af13d1a088..53e8a75ad755 100644 --- a/src/ServiceManagement/StorSimple/Commands.StorSimple/Microsoft.WindowsAzure.Commands.StorSimple.dll-help.psd1 +++ b/src/ServiceManagement/StorSimple/Commands.StorSimple/Microsoft.WindowsAzure.Commands.StorSimple.dll-help.psd1 @@ -83,6 +83,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/Commands.TrafficManager.Test.csproj b/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/Commands.TrafficManager.Test.csproj index b09dcc62e023..d1e6f52cd17c 100644 --- a/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/Commands.TrafficManager.Test.csproj +++ b/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/Commands.TrafficManager.Test.csproj @@ -99,9 +99,9 @@ ..\..\..\packages\Microsoft.WindowsAzure.Management.TrafficManager.0.16.0-preview\lib\net40\Microsoft.WindowsAzure.Management.TrafficManager.dll - + False - ..\..\..\packages\Moq.4.2.1402.2112\lib\net40\Moq.dll + ..\..\..\packages\Moq.4.2.1510.2205\lib\net40\Moq.dll False diff --git a/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/packages.config b/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/packages.config index dfa7364aedca..3d6ff2b2bef6 100644 --- a/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/packages.config +++ b/src/ServiceManagement/TrafficManager/Commands.TrafficManager.Test/packages.config @@ -17,7 +17,7 @@ - + diff --git a/src/ServiceManagement/TrafficManager/Commands.TrafficManager/Microsoft.WindowsAzure.Commands.TrafficManager.dll-help.psd1 b/src/ServiceManagement/TrafficManager/Commands.TrafficManager/Microsoft.WindowsAzure.Commands.TrafficManager.dll-help.psd1 index de022ae50496..48b7bee3e1a3 100644 --- a/src/ServiceManagement/TrafficManager/Commands.TrafficManager/Microsoft.WindowsAzure.Commands.TrafficManager.dll-help.psd1 +++ b/src/ServiceManagement/TrafficManager/Commands.TrafficManager/Microsoft.WindowsAzure.Commands.TrafficManager.dll-help.psd1 @@ -81,6 +81,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/tools/AzureRM/AzureRM.psd1 b/tools/AzureRM/AzureRM.psd1 index 7d1348974c78..36e97ea3debc 100644 --- a/tools/AzureRM/AzureRM.psd1 +++ b/tools/AzureRM/AzureRM.psd1 @@ -87,6 +87,27 @@ ModuleList = @() FileList = @() # Private data to pass to the module specified in ModuleToProcess -PrivateData = '' +PrivateData = @{ + + PSData = @{ + + # Tags applied to this module. These help with module discovery in online galleries. + # Tags = @() + + # A URL to the license for this module. + LicenseUri = 'https://raw.githubusercontent.com/Azure/azure-powershell/dev/LICENSE.txt' + + # A URL to the main website for this project. + ProjectUri = 'https://github.com/Azure/azure-powershell' + + # A URL to an icon representing this module. + # IconUri = '' + + # ReleaseNotes of this module + ReleaseNotes = 'https://github.com/Azure/azure-powershell/blob/dev/ChangeLog.md' + + } # End of PSData hashtable + +} # End of PrivateData hashtable } diff --git a/tools/PublishModules.ps1 b/tools/PublishModules.ps1 index 01517bc13f82..08591e98e748 100644 --- a/tools/PublishModules.ps1 +++ b/tools/PublishModules.ps1 @@ -58,7 +58,7 @@ $publishToLocal = test-path $repositoryLocation if (($scope -eq 'All') -or $publishToLocal ) { # If we publish 'All' or to local folder, publish AzureRM.Profile first, becasue it is the common dependency Write-Host "Publishing profile module" - Publish-Module -Path "$resourceManagerRootFolder\AzureRM.Profile" -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path "$resourceManagerRootFolder\AzureRM.Profile" -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") Write-Host "Published profile module" } @@ -66,21 +66,21 @@ if (($scope -eq 'All') -or ($scope -eq 'ServiceManagement')) { $modulePath = "$packageFolder\$buildConfig\ServiceManagement\Azure" # Publish Azure module Write-Host "Publishing ServiceManagement(aka Azure) module from $modulePath" - Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") } if (($scope -eq 'All') -or ($scope -eq 'AzureStorage')) { $modulePath = "$packageFolder\$buildConfig\ServiceManagement\Azure\Azure.Storage" # Publish AzureStorage module Write-Host "Publishing AzureStorage module from $modulePath" - Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") } if (($scope -eq 'All') -or ($scope -eq 'AzureRM')) { # Publish AzureRM module $modulePath = "$PSScriptRoot\AzureRM" Write-Host "Publishing AzureRM module from $modulePath" - Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") Write-Host "Published Azure module" } @@ -92,7 +92,7 @@ if ($scope -eq 'All') { if (($module.Name -ne "AzureRM.Profile") -and ($module.Name -ne "Azure.Storage")) { $modulePath = $module.FullName Write-Host "Publishing $module module from $modulePath" - Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") Write-Host "Published $module module" } } @@ -100,7 +100,7 @@ if ($scope -eq 'All') { $modulePath = Join-Path $resourceManagerRootFolder "AzureRM.$scope" if (Test-Path $modulePath) { Write-Host "Publishing $scope module from $modulePath" - Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") -LicenseUri "http://aka.ms/azps-license" + Publish-Module -Path $modulePath -NuGetApiKey $apiKey -Repository $repoName -Tags ("Azure") Write-Host "Published $scope module" } else { Write-Error "Can not find module with name $scope to publish"