Storage Discovery General Availability Release (#28571)

Co-authored-by: Shane Fu <[email protected]>

Author: shanefujs

src/StorageDiscovery/StorageDiscovery.Autorest/UX/Microsoft.StorageDiscovery/storageDiscoveryWorkspaces.json

@@ -1,6 +1,6 @@
 {
   "resourceType": "storageDiscoveryWorkspaces",
-  "apiVersion": "2025-06-01-preview",
+  "apiVersion": "2025-09-01",
   "learnMore": {
     "url": "https://learn.microsoft.com/powershell/module/az.storagediscovery"
   },

src/StorageDiscovery/StorageDiscovery.Autorest/custom/Az.StorageDiscovery.custom.psm1

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

src/StorageDiscovery/StorageDiscovery.Autorest/custom/README.md

@@ -1,5 +1,5 @@
 # Custom
-This directory contains custom implementation for non-generated cmdlets for the `Az.StorageDiscovery` 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.StorageDiscovery.custom.psm1`. This file should not be modified.
+This directory contains custom implementation for non-generated cmdlets for the `Az.StorageDiscovery` 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.StorageDiscovery.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.StorageDiscovery.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.StorageDiscovery.DoNotExportAttribute`
   - Used in C# and script cmdlets to suppress creating an exported cmdlet at build-time. These cmdlets will *not be exposed* by `Az.StorageDiscovery`.
 - `Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.InternalExportAttribute`
-  - Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.StorageDiscovery`. 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.StorageDiscovery`. For more information, see [README.md](../internal/README.md) in the `../internal` folder.
 - `Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.ProfileAttribute`
   - Used in C# and script cmdlets to define which Azure profiles the cmdlet supports. This is only supported for Azure (`--azure`) modules.

src/StorageDiscovery/StorageDiscovery.Autorest/custom/autogen-model-cmdlets/New-AzStorageDiscoveryScopeObject.ps1

@@ -39,7 +39,7 @@ function New-AzStorageDiscoveryScopeObject {
         [string[]]
         $ResourceType,
         [Parameter(HelpMessage="Resource tags.")]
-        [Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.Models.ITags]
+        [Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.Models.IStorageDiscoveryScopeTags]
         $Tag,
         [Parameter(HelpMessage="The storage account tags keys to filter.")]
         [string[]]

src/StorageDiscovery/StorageDiscovery.Autorest/docs/Az.StorageDiscovery.md

@@ -1,6 +1,6 @@
 ---
 Module Name: Az.StorageDiscovery
-Module Guid: d88ebaf3-95a8-4142-a582-f2526d777a7c
+Module Guid: e862cfcb-5844-4c82-afae-b23fdfd67bdd
 Download Help Link: https://learn.microsoft.com/powershell/module/az.storagediscovery
 Help Version: 1.0.0.0
 Locale: en-US

src/StorageDiscovery/StorageDiscovery.Autorest/docs/New-AzStorageDiscoveryScopeObject.md

@@ -13,8 +13,8 @@ Create an in-memory object for StorageDiscoveryScope.
 ## SYNTAX
 
 ```
-New-AzStorageDiscoveryScopeObject -DisplayName <String> -ResourceType <String[]> [-Tag <ITags>]
- [-TagKeysOnly <String[]>] [<CommonParameters>]
+New-AzStorageDiscoveryScopeObject -DisplayName <String> -ResourceType <String[]>
+ [-Tag <IStorageDiscoveryScopeTags>] [-TagKeysOnly <String[]>] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -95,7 +95,7 @@ Accept wildcard characters: False
 Resource tags.
 
 ```yaml
-Type: Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.Models.ITags
+Type: Microsoft.Azure.PowerShell.Cmdlets.StorageDiscovery.Models.IStorageDiscoveryScopeTags
 Parameter Sets: (All)
 Aliases:
 

src/StorageDiscovery/StorageDiscovery.Autorest/docs/README.md

@@ -1,5 +1,5 @@
 # Docs
-This directory contains the documentation of the cmdlets for the `Az.StorageDiscovery` 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.StorageDiscovery` 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.StorageDisc
 - Packaged: yes
 
 ## Details
-The process of documentation generation loads `Az.StorageDiscovery` 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.StorageDiscovery` 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/StorageDiscovery/StorageDiscovery.Autorest/generate-info.json

@@ -1,3 +1,3 @@
 {
-  "generate_Id": "60c9a46f-76b7-4bd5-8af2-72f8ed0c8de7"
+  "generate_Id": "78baa472-4432-4cbd-bb45-39983c7e1ac6"
 }

src/StorageDiscovery/StorageDiscovery.Autorest/resources/README.md

@@ -1,5 +1,5 @@
 # Resources
-This directory can contain any additional resources for module that are not required at runtime. This directory **does not** get packaged with the module. If you have assets for custom implementation, place them into the `..\custom` folder.
+This directory can contain any additional resources for module that are not required at runtime. This directory **does not** get packaged with the module. If you have assets for custom implementation, place them into the `../custom` folder.
 
 ## Info
 - Modifiable: yes