Migrate workloads monitor to autorest v4 (#28740)

Author: jaskisin

src/Workloads/Monitors.Autorest/Properties/AssemblyInfo.cs

@@ -24,3 +24,6 @@
 [assembly: System.Reflection.AssemblyVersionAttribute("1.0.0")]
 [assembly: System.Runtime.InteropServices.ComVisibleAttribute(false)]
 [assembly: System.CLSCompliantAttribute(false)]
+
+
+

src/Workloads/Monitors.Autorest/custom/Az.Monitors.custom.psm1

@@ -1,9 +1,9 @@
 # region Generated 
   # Load the private module dll
-  $null = Import-Module -PassThru -Name (Join-Path $PSScriptRoot '..\bin\Az.Monitors.private.dll')
+  $null = Import-Module -PassThru -Name (Join-Path $PSScriptRoot '../bin/Az.Monitors.private.dll')
 
   # Load the internal module
-  $internalModulePath = Join-Path $PSScriptRoot '..\internal\Az.Monitors.internal.psm1'
+  $internalModulePath = Join-Path $PSScriptRoot '../internal/Az.Monitors.internal.psm1'
   if(Test-Path $internalModulePath) {
     $null = Import-Module -Name $internalModulePath
   }

src/Workloads/Monitors.Autorest/custom/README.md

@@ -1,5 +1,5 @@
 # Custom
-This directory contains custom implementation for non-generated cmdlets for the `Az.Monitors` 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.Monitors.custom.psm1`. This file should not be modified.
+This directory contains custom implementation for non-generated cmdlets for the `Az.Monitors` 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.Monitors.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.Monitors.custom.psm1`. Then, during the build process, this module is loaded and processed in the same manner as the C# cmdlets. The fundamental 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
@@ -36,6 +36,6 @@ For processing the cmdlets, we've created some additional attributes:
 - `Microsoft.Azure.PowerShell.Cmdlets.Workloads.Monitors.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.Monitors`.
 - `Microsoft.Azure.PowerShell.Cmdlets.Workloads.Monitors.InternalExportAttribute`
-  - Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.Monitors`. 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.Monitors`. For more information, see [README.md](../internal/README.md) in the `../internal` folder.
 - `Microsoft.Azure.PowerShell.Cmdlets.Workloads.Monitors.ProfileAttribute`
   - Used in C# and script cmdlets to define which Azure profiles the cmdlet supports. This is only supported for Azure (`--azure`) modules.

src/Workloads/Monitors.Autorest/docs/Az.Monitors.md

@@ -1,6 +1,6 @@
 ---
 Module Name: Az.Monitors
-Module Guid: c2b5aac3-3ae4-4fa4-9d6a-b7a7834ba0ba
+Module Guid: d805f2ff-7f5f-4e5c-aa61-59be1b0c5ad4
 Download Help Link: https://learn.microsoft.com/powershell/module/az.monitors
 Help Version: 1.0.0.0
 Locale: en-US

src/Workloads/Monitors.Autorest/docs/New-AzWorkloadsProviderInstance.md

@@ -50,8 +50,7 @@ Create a provider instance for the specified subscription, resource group, SAP m
 ### Example 1: Create a new provider
 ```powershell
 $providerSetting = New-AzWorkloadsProviderSqlServerInstanceObject -Password '<password>' -Port 1433 -Username '<username>' -Hostname 10.1.14.5 -SapSid X00 -SslPreference Disabled
-        $providerSetting.ProviderType | Should -Be "MsSqlServer"
-        
+
 New-AzWorkloadsProviderInstance -MonitorName suha-0202-ams9 -Name sql-prov-1 -ResourceGroupName suha-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting $providerSetting
 ```
 

src/Workloads/Monitors.Autorest/docs/README.md

@@ -1,5 +1,5 @@
 # Docs
-This directory contains the documentation of the cmdlets for the `Az.Monitors` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden on regeneration*. To update documentation examples, please use the `..\examples` folder.
+This directory contains the documentation of the cmdlets for the `Az.Monitors` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden 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.Monitors` m
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.Monitors` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.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.Monitors` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.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.

src/Workloads/Monitors.Autorest/docs/Update-AzWorkloadsMonitor.md

@@ -115,7 +115,7 @@ Accept wildcard characters: False
 Determines whether to enable a system-assigned identity for the resource.
 
 ```yaml
-Type: System.Nullable`1[[System.Boolean, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]
+Type: System.Nullable`1[[System.Boolean, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]
 Parameter Sets: (All)
 Aliases:
 

src/Workloads/Monitors.Autorest/docs/Update-AzWorkloadsProviderInstance.md

@@ -40,27 +40,33 @@ Update a provider instance for the specified subscription, resource group, SAP m
 
 ## EXAMPLES
 
-### Example 1: {{ Add title here }}
+### Example 1: Update an existing provider
 ```powershell
-{{ Add code here }}
+$providerSetting = New-AzWorkloadsProviderSqlServerInstanceObject -Password '<password>' -Port 1433 -Username '<username>' -Hostname 10.1.14.5 -SapSid X00 -SslPreference Disabled
+
+Update-AzWorkloadsProviderInstance -MonitorName sap-0202-ams9 -Name sql-prov-1 -ResourceGroupName sap-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting $providerSetting
 ```
 
 ```output
-{{ Add output here (remove the output block if the example doesn't have an output) }}
+Name       ResourceGroupName ProvisioningState IdentityType
+----       ----------------- ----------------- ------------
+sql-prov-1 sap-0802-rg1     Succeeded
 ```
 
-{{ Add description here }}
+Update an existing provider for a specific AMS instance
 
-### Example 2: {{ Add title here }}
+### Example 2: Update an existing provider by Id
 ```powershell
-{{ Add code here }}
+Update-AzWorkloadsProviderInstance -MonitorName sap-160323-ams4 -Name sap-sql-3 -ResourceGroupName sap-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting '{"sslPreference":"Disabled","providerType":"MsSqlServer","hostname":"10.1.14.5","sapSid":"X00","dbPort":"1433","dbUsername":"","dbPassword":""}'
 ```
 
 ```output
-{{ Add output here (remove the output block if the example doesn't have an output) }}
+Name       ResourceGroupName ProvisioningState IdentityType
+----       ----------------- ----------------- ------------
+sap-sql-3 sap-0802-rg1     Succeeded
 ```
 
-{{ Add description here }}
+Update an existing provider for a specific AMS instance by Arm Id
 
 ## PARAMETERS
 
@@ -99,7 +105,7 @@ Accept wildcard characters: False
 Determines whether to enable a system-assigned identity for the resource.
 
 ```yaml
-Type: System.Nullable`1[[System.Boolean, System.Private.CoreLib, Version=9.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]
+Type: System.Nullable`1[[System.Boolean, System.Private.CoreLib, Version=6.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]
 Parameter Sets: (All)
 Aliases:
 

src/Workloads/Monitors.Autorest/examples/New-AzWorkloadsProviderInstance.md

@@ -1,8 +1,7 @@
 ### Example 1: Create a new provider
 ```powershell
 $providerSetting = New-AzWorkloadsProviderSqlServerInstanceObject -Password '<password>' -Port 1433 -Username '<username>' -Hostname 10.1.14.5 -SapSid X00 -SslPreference Disabled
-        $providerSetting.ProviderType | Should -Be "MsSqlServer"
-        
+
 New-AzWorkloadsProviderInstance -MonitorName suha-0202-ams9 -Name sql-prov-1 -ResourceGroupName suha-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting $providerSetting
 ```
 
@@ -26,4 +25,3 @@ suha-sql-3 suha-0802-rg1     Succeeded
 ```
 
 Creates a new provider for a specific AMS instance by Arm Id
-

src/Workloads/Monitors.Autorest/examples/Update-AzWorkloadsProviderInstance.md

@@ -1,22 +1,27 @@
-### Example 1: {{ Add title here }}
+### Example 1: Update an existing provider
 ```powershell
-{{ Add code here }}
+$providerSetting = New-AzWorkloadsProviderSqlServerInstanceObject -Password '<password>' -Port 1433 -Username '<username>' -Hostname 10.1.14.5 -SapSid X00 -SslPreference Disabled
+
+Update-AzWorkloadsProviderInstance -MonitorName sap-0202-ams9 -Name sql-prov-1 -ResourceGroupName sap-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting $providerSetting
 ```
 
 ```output
-{{ Add output here (remove the output block if the example doesn't have an output) }}
+Name       ResourceGroupName ProvisioningState IdentityType
+----       ----------------- ----------------- ------------
+sql-prov-1 sap-0802-rg1     Succeeded
 ```
 
-{{ Add description here }}
+Update an existing provider for a specific AMS instance
 
-### Example 2: {{ Add title here }}
+### Example 2: Update an existing provider by Id
 ```powershell
-{{ Add code here }}
+Update-AzWorkloadsProviderInstance -MonitorName sap-160323-ams4 -Name sap-sql-3 -ResourceGroupName sap-0802-rg1 -SubscriptionId 49d64d54-e966-4c46-a868-1999802b762c -ProviderSetting '{"sslPreference":"Disabled","providerType":"MsSqlServer","hostname":"10.1.14.5","sapSid":"X00","dbPort":"1433","dbUsername":"","dbPassword":""}'
 ```
 
 ```output
-{{ Add output here (remove the output block if the example doesn't have an output) }}
+Name       ResourceGroupName ProvisioningState IdentityType
+----       ----------------- ----------------- ------------
+sap-sql-3 sap-0802-rg1     Succeeded
 ```
 
-{{ Add description here }}
-
+Update an existing provider for a specific AMS instance by Arm Id