Update GA module versions and regenerate (#15518)

isra-fel · web-flow · commit ed61d7622a50 · 2021-07-22T22:02:12.000+08:00
* update version and regen

* fix urls
diff --git a/src/AppConfiguration/.gitignore b/src/AppConfiguration/.gitignore
@@ -6,6 +6,7 @@ internal
 exports
 tools
 custom/*.psm1
+custom/autogen-model-cmdlets
 test/*-TestResults.xml
 /*.ps1
 /*.ps1xml
diff --git a/src/AppConfiguration/Az.AppConfiguration.psd1 b/src/AppConfiguration/Az.AppConfiguration.psd1
@@ -1,7 +1,7 @@
 @{
   GUID = '3ff16738-381e-4d5a-9d90-c7ef6816f78e'
   RootModule = './Az.AppConfiguration.psm1'
-  ModuleVersion = '0.2.0'
+  ModuleVersion = '1.0.0'
   CompatiblePSEditions = 'Core', 'Desktop'
   Author = 'Microsoft Corporation'
   CompanyName = 'Microsoft Corporation'
diff --git a/src/AppConfiguration/custom/readme.md b/src/AppConfiguration/custom/readme.md
@@ -31,11 +31,11 @@ These provide functionality to our HTTP pipeline and other useful features. In s
 
 ### Attributes
 For processing the cmdlets, we've created some additional attributes:
-- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.Models.DescriptionAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.DescriptionAttribute`
   - Used in C# cmdlets to provide a high-level description of the cmdlet. This is propegated to reference documentation via [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) in the exported scripts.
-- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.Models.DoNotExportAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.AppConfiguration`.
-- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.Models.InternalExportAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.InternalExportAttribute`
   - Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.AppConfiguration`. For more information, see [readme.md](..\internal/readme.md) in the `..\internal` folder.
-- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.Models.ProfileAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.AppConfiguration.ProfileAttribute`
   - Used in C# and script cmdlets to define which Azure profiles the cmdlet supports. This is only supported for Azure (`--azure`) modules.
diff --git a/src/AppConfiguration/readme.md b/src/AppConfiguration/readme.md
@@ -17,7 +17,7 @@ This directory contains the PowerShell module for the AppConfiguration service.
 This module was primarily generated via [AutoRest](https://github.com/Azure/autorest) using the [PowerShell](https://github.com/Azure/autorest.powershell) extension.
 
 ## Module Requirements
-- [Az.Accounts module](https://www.powershellgallery.com/packages/Az.Accounts/), version 1.8.1 or greater
+- [Az.Accounts module](https://www.powershellgallery.com/packages/Az.Accounts/), version 2.2.3 or greater
 
 ## Authentication
 AutoRest does not generate authentication code for the module. Authentication is handled via Az.Accounts by altering the HTTP payload before it is sent.
@@ -53,7 +53,7 @@ require:
 input-file:
   - https://github.com/Azure/azure-rest-api-specs/blob/5d7c9b734d462cc3b111757957c7d2cc027dff80/specification/appconfiguration/resource-manager/Microsoft.AppConfiguration/stable/2020-06-01/appconfiguration.json
 
-module-version: 0.2.0
+module-version: 1.0.0
 title: AppConfiguration
 
 # If there are post APIs for some kinds of actions in the RP, you may need to
diff --git a/src/AppConfiguration/utils/Unprotect-SecureString.ps1 b/src/AppConfiguration/utils/Unprotect-SecureString.ps1
@@ -0,0 +1,16 @@
+#This script converts securestring to plaintext
+
+param(
+    [Parameter(Mandatory, ValueFromPipeline)]
+    [System.Security.SecureString]
+    ${SecureString}
+)
+
+$ssPtr = [System.Runtime.InteropServices.Marshal]::SecureStringToBSTR($SecureString)
+try {
+    $plaintext = [System.Runtime.InteropServices.Marshal]::PtrToStringBSTR($ssPtr)
+} finally {
+    [System.Runtime.InteropServices.Marshal]::ZeroFreeBSTR($ssPtr)
+}
+
+return $plaintext
diff --git a/src/Databricks/.gitignore b/src/Databricks/.gitignore
@@ -6,6 +6,7 @@ internal
 exports
 tools
 custom/*.psm1
+custom/autogen-model-cmdlets
 test/*-TestResults.xml
 /*.ps1
 /*.ps1xml
diff --git a/src/Databricks/Az.Databricks.psd1 b/src/Databricks/Az.Databricks.psd1
@@ -1,7 +1,7 @@
 @{
   GUID = 'b453c0c1-7867-4fa1-9fd0-0cf8f6c6959c'
   RootModule = './Az.Databricks.psm1'
-  ModuleVersion = '0.2.0'
+  ModuleVersion = '1.1.0'
   CompatiblePSEditions = 'Core', 'Desktop'
   Author = 'Microsoft Corporation'
   CompanyName = 'Microsoft Corporation'
diff --git a/src/Databricks/readme.md b/src/Databricks/readme.md
@@ -53,7 +53,7 @@ require:
 input-file:
   - https://github.com/Azure/azure-rest-api-specs/blob/9120c925c8de6840da38365bb8807be2e0e617c0/specification/databricks/resource-manager/Microsoft.Databricks/stable/2018-04-01/databricks.json
 
-module-version: 0.2.0
+module-version: 1.1.0
 title: Databricks
 subject-prefix: $(service-name)
 
diff --git a/src/Kusto/Az.Kusto.psd1 b/src/Kusto/Az.Kusto.psd1
@@ -1,7 +1,7 @@
 @{
   GUID = '18c61846-f6f0-425e-ba4b-5cf903e2bdd8'
   RootModule = './Az.Kusto.psm1'
-  ModuleVersion = '0.1.4'
+  ModuleVersion = '2.0.0'
   CompatiblePSEditions = 'Core', 'Desktop'
   Author = 'Microsoft Corporation'
   CompanyName = 'Microsoft Corporation'
diff --git a/src/Kusto/custom/readme.md b/src/Kusto/custom/readme.md
@@ -32,7 +32,7 @@ These provide functionality to our HTTP pipeline and other useful features. In s
 ### Attributes
 For processing the cmdlets, we've created some additional attributes:
 - `Microsoft.Azure.PowerShell.Cmdlets.Kusto.DescriptionAttribute`
-  - Used in C# cmdlets to provide a high-level description of the cmdlet. This is propegated to reference documentation via [help comments](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_comment_based_help) in the exported scripts.
+  - Used in C# cmdlets to provide a high-level description of the cmdlet. This is propegated to reference documentation via [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) in the exported scripts.
 - `Microsoft.Azure.PowerShell.Cmdlets.Kusto.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.Kusto`.
 - `Microsoft.Azure.PowerShell.Cmdlets.Kusto.InternalExportAttribute`
diff --git a/src/Kusto/docs/readme.md b/src/Kusto/docs/readme.md
@@ -8,4 +8,4 @@ This directory contains the documentation of the cmdlets for the `Az.Kusto` modu
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.Kusto` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
+The process of documentation generation loads `Az.Kusto` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
diff --git a/src/Kusto/how-to.md b/src/Kusto/how-to.md
@@ -14,7 +14,7 @@ To generate documentation, the process is now integrated into the `build-module.
 To test the cmdlets, we use [Pester](https://github.com/pester/Pester). Tests scripts (`.ps1`) should be added to the `test` folder. To execute the Pester tests, run the `test-module.ps1` script. This will run all tests in `playback` mode within the `test` folder. To read more about testing cmdlets, look at the [readme.md](examples/readme.md) in the `examples` folder.
 
 ## Packing `Az.Kusto`
-To pack `Az.Kusto` for distribution, run the `pack-module.ps1` script. This will take the contents of multiple directories and certain root-folder files to create a `.nupkg`. The structure of the `.nupkg` is created so it can be loaded part of a [PSRepository](https://docs.microsoft.com/en-us/powershell/module/powershellget/register-psrepository). Additionally, this package is in a format for distribution to the [PSGallery](https://www.powershellgallery.com/). For signing an Azure module, please contact the [Azure PowerShell](https://github.com/Azure/azure-powershell) team.
+To pack `Az.Kusto` for distribution, run the `pack-module.ps1` script. This will take the contents of multiple directories and certain root-folder files to create a `.nupkg`. The structure of the `.nupkg` is created so it can be loaded part of a [PSRepository](https://docs.microsoft.com/powershell/module/powershellget/register-psrepository). Additionally, this package is in a format for distribution to the [PSGallery](https://www.powershellgallery.com/). For signing an Azure module, please contact the [Azure PowerShell](https://github.com/Azure/azure-powershell) team.
 
 ## Module Script Details
 There are multiple scripts created for performing different actions for developing `Az.Kusto`.
diff --git a/src/Kusto/readme.md b/src/Kusto/readme.md
@@ -59,7 +59,7 @@ input-file:
 
 > Names
 ``` yaml
-module-version: 0.1.4
+module-version: 2.0.0
 title: Kusto
 subject-prefix: $(service-name)
 ```
diff --git a/src/Kusto/tools/Resources/docs/readme.md b/src/Kusto/tools/Resources/docs/readme.md
@@ -8,4 +8,4 @@ This directory contains the documentation of the cmdlets for the `Az.Resources`
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.Resources` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
+The process of documentation generation loads `Az.Resources` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
diff --git a/src/Kusto/tools/Resources/how-to.md b/src/Kusto/tools/Resources/how-to.md
@@ -14,7 +14,7 @@ To generate documentation, the process is now integrated into the `build-module.
 To test the cmdlets, we use [Pester](https://github.com/pester/Pester). Tests scripts (`.ps1`) should be added to the `test` folder. To execute the Pester tests, run the `test-module.ps1` script. This will run all tests in `playback` mode within the `test` folder. To read more about testing cmdlets, look at the [readme.md](examples/readme.md) in the `examples` folder.
 
 ## Packing `Az.Resources`
-To pack `Az.Resources` for distribution, run the `pack-module.ps1` script. This will take the contents of multiple directories and certain root-folder files to create a `.nupkg`. The structure of the `.nupkg` is created so it can be loaded part of a [PSRepository](https://docs.microsoft.com/en-us/powershell/module/powershellget/register-psrepository). Additionally, this package is in a format for distribution to the [PSGallery](https://www.powershellgallery.com/). For signing an Azure module, please contact the [Azure PowerShell](https://github.com/Azure/azure-powershell) team.
+To pack `Az.Resources` for distribution, run the `pack-module.ps1` script. This will take the contents of multiple directories and certain root-folder files to create a `.nupkg`. The structure of the `.nupkg` is created so it can be loaded part of a [PSRepository](https://docs.microsoft.com/powershell/module/powershellget/register-psrepository). Additionally, this package is in a format for distribution to the [PSGallery](https://www.powershellgallery.com/). For signing an Azure module, please contact the [Azure PowerShell](https://github.com/Azure/azure-powershell) team.
 
 ## Module Script Details
 There are multiple scripts created for performing different actions for developing `Az.Resources`.
diff --git a/src/ResourceMover/.gitignore b/src/ResourceMover/.gitignore
@@ -6,6 +6,7 @@ internal
 exports
 tools
 custom/*.psm1
+custom/autogen-model-cmdlets
 test/*-TestResults.xml
 /*.ps1
 /*.ps1xml
diff --git a/src/ResourceMover/Az.ResourceMover.psd1 b/src/ResourceMover/Az.ResourceMover.psd1
@@ -1,7 +1,7 @@
 @{
   GUID = '97d87543-8eef-4574-a70d-7317ec4abe54'
   RootModule = './Az.ResourceMover.psm1'
-  ModuleVersion = '0.1.0'
+  ModuleVersion = '1.0.0'
   CompatiblePSEditions = 'Core', 'Desktop'
   Author = 'Microsoft Corporation'
   CompanyName = 'Microsoft Corporation'
diff --git a/src/ResourceMover/custom/readme.md b/src/ResourceMover/custom/readme.md
@@ -1,5 +1,5 @@
 # Custom
-This directory contains custom implementation for non-generated cmdlets for the `Az.ResourceMover` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `../exports` folder. The only generated file into this folder is the `Az.ResourceMover.custom.psm1`. This file should not be modified.
+This directory contains custom implementation for non-generated cmdlets for the `Az.ResourceMover` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `..\exports` folder. The only generated file into this folder is the `Az.ResourceMover.custom.psm1`. This file should not be modified.
 
 ## Info
 - Modifiable: yes
@@ -15,10 +15,10 @@ For C# cmdlets, they are compiled with the rest of the generated low-level cmdle
 For script cmdlets, these are loaded via the `Az.ResourceMover.custom.psm1`. Then, during the build process, this module is loaded and processed in the same manner as the C# cmdlets. The fundemental difference is the script cmdlets use the `ParameterSetName` attribute and C# cmdlets do not. To create a script cmdlet variant of a generated cmdlet, simply decorate all parameters in the script with the new `ParameterSetName` in the `Parameter` attribute. This will appropriately treat each parameter set as a separate variant when processed to be exported during the build.
 
 ## Purpose
-This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `../exports` folder.
+This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `..\exports` folder.
 
 ## Usage
-The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `../exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
+The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `..\exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
 - Break
 - DefaultProfile
 - HttpPipelineAppend
@@ -31,11 +31,11 @@ These provide functionality to our HTTP pipeline and other useful features. In s
 
 ### Attributes
 For processing the cmdlets, we've created some additional attributes:
-- `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.Models.DescriptionAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.DescriptionAttribute`
   - Used in C# cmdlets to provide a high-level description of the cmdlet. This is propegated to reference documentation via [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) in the exported scripts.
-- `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.Models.DoNotExportAttribute`
+- `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.ResourceMover`.
 - `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.InternalExportAttribute`
-  - Used in C# cmdlets to route exported cmdlets to the `../internal`, which are *not exposed* by `Az.ResourceMover`. For more information, see [readme.md](../internal/readme.md) in the `../internal` folder.
+  - Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.ResourceMover`. For more information, see [readme.md](..\internal/readme.md) in the `..\internal` folder.
 - `Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.ProfileAttribute`
   - Used in C# and script cmdlets to define which Azure profiles the cmdlet supports. This is only supported for Azure (`--azure`) modules.
diff --git a/src/ResourceMover/docs/Get-AzResourceMoverRequiredForResources.md b/src/ResourceMover/docs/Get-AzResourceMoverRequiredForResources.md
@@ -1,7 +1,7 @@
 ---
 external help file:
 Module Name: Az.ResourceMover
-online version: https://docs.microsoft.com/en-us/powershell/module/az.resourcemover/get-azresourcemoverrequiredforresources
+online version: https://docs.microsoft.com/powershell/module/az.resourcemover/get-azresourcemoverrequiredforresources
 schema: 2.0.0
 ---
 
diff --git a/src/ResourceMover/docs/Invoke-AzResourceMoverBulkRemove.md b/src/ResourceMover/docs/Invoke-AzResourceMoverBulkRemove.md
@@ -1,7 +1,7 @@
 ---
 external help file:
 Module Name: Az.ResourceMover
-online version: https://docs.microsoft.com/en-us/powershell/module/az.resourcemover/invoke-azresourcemoverbulkremove
+online version: https://docs.microsoft.com/powershell/module/az.resourcemover/invoke-azresourcemoverbulkremove
 schema: 2.0.0
 ---
 
diff --git a/src/ResourceMover/docs/readme.md b/src/ResourceMover/docs/readme.md
@@ -1,5 +1,5 @@
 # Docs
-This directory contains the documentation of the cmdlets for the `Az.ResourceMover` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overriden on regeneration*. To update documentation examples, please use the `../examples` folder.
+This directory contains the documentation of the cmdlets for the `Az.ResourceMover` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overriden on regeneration*. To update documentation examples, please use the `..\examples` folder.
 
 ## Info
 - Modifiable: no
@@ -8,4 +8,4 @@ This directory contains the documentation of the cmdlets for the `Az.ResourceMov
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.ResourceMover` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `../exports` folder. Additionally, when writing custom cmdlets in the `../custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `../examples` folder.
+The process of documentation generation loads `Az.ResourceMover` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
diff --git a/src/ResourceMover/readme.md b/src/ResourceMover/readme.md
@@ -63,7 +63,7 @@ output-folder: .
 aks: $(repo)/specification/resourcemover/resource-manager/Microsoft.Migrate/stable/2021-01-01
 input-file:
 	- $(aks)/resourcemovercollection.json
-module-version: 0.1.0
+module-version: 1.0.0
 
 directive:
   # Remove the unexpanded parameter set
diff --git a/src/ResourceMover/resources/readme.md b/src/ResourceMover/resources/readme.md
diff --git a/src/ResourceMover/test/readme.md b/src/ResourceMover/test/readme.md
