Merge branch 'yslin/cu_ga_sdk_tsp_client' of https://github.com/Azure/azure-sdk-for-net into changjian-wang/improve_tests_for_cu_ga_sdk_tsp_client

Author: Changjian Wang

.github/CODEOWNERS

@@ -796,11 +796,10 @@
 # ServiceOwners:                                                   @axisc @sjkwak @hmlam
 
 # PRLabel: %Search
-/sdk/search/                                                       @Azure/azure-sdk-write-search @Azure/azsdk-search
+/sdk/search/                                                       @Azure/azure-sdk-write-search
 
 # ServiceLabel: %Search
-# AzureSdkOwners:                                                  @ShivangiReja
-# ServiceOwners:                                                   @kuanlu95 @mattgotteiner
+# ServiceOwners:                                                   @efrainretana @kuanlu95 @mattgotteiner
 
 # ServiceLabel: %Security
 # ServiceOwners:                                                   @chlahav
@@ -1007,10 +1006,7 @@
 # ServiceOwners:                                                   @emmeliaAra
 
 # PRLabel: %HybridConnectivity
-/sdk/hybridconnectivity/Azure.ResourceManager.*/                   @apmehrotra
-
-# ServiceLabel: %HybridConnectivity %Mgmt
-# ServiceOwners:                                                   @apmehrotra
+/sdk/hybridconnectivity/Azure.ResourceManager.*/                   @ArcturusZhang @ArthurMa1978
 
 # PRLabel: %LambdaTest HyperExecute
 /sdk/lambdatesthyperexecute/Azure.ResourceManager.*/               @ArcturusZhang @ArthurMa1978

doc/DataPlaneCodeGeneration/AzureSDKGeneration_Prerequistites.md

@@ -16,4 +16,4 @@ Make sure you have a TypeSpec project in the `main` branch of the public API spe
 
 ## Set up SDK Project Folder
 
-You will need to generate the SDK library under an SDK project folder following the repository [guidelines](https://github.com/Azure/azure-sdk-for-net/blob/main/doc/DataPlaneCodeGeneration/AzureSDKPackage_Setup.md).
+You will need to generate the SDK library under an SDK project folder following the repository guidelines. You can use the [Azure.Template](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/template/Azure.Template) as an example.

doc/DataPlaneCodeGeneration/AzureSDKPackage_Setup.md

@@ -18,31 +18,40 @@ sdk\<service name>\<package name>\<package name>.sln
 
 ## Create sdk package
 
-We will use the Azure SDK template [Azure.Template](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/template/Azure.Template) to create the initial project skeleton for SDKs generated from TypeSpec.
+You have several options to create the initial project skeleton for SDKs generated from TypeSpec:
 
-You can run `eng\scripts\automation\Invoke-TypeSpecDataPlaneGenerateSDKPackage.ps1` to generate the starting SDK client library package directly as following:
+### Option 1: Using tsp-client init (Recommended)
 
-```powershell
-eng/scripts/automation/Invoke-TypeSpecDataPlaneGenerateSDKPackage.ps1 -sdkFolder <sdk-folder-path> -typespecSpecDirectory <relativeTypeSpecProjectFolderPath> -commit <commitId> [-repo <specRepo>] [-additionalSubDirectories <relativeFolders>]
+You can use the `tsp-client init` command to initialize the TypeSpec configuration. This tool automatically sets up the correct emitter path for new services. You must pass the `--tsp-config` parameter pointing to the tspconfig.yaml in the spec repo:
+
+```bash
+tsp-client init --tsp-config https://github.com/Azure/azure-rest-api-specs/blob/<commit>/specification/<service>/<typespec-project-folder>/tspconfig.yaml
 ```
 
-e.g.
-Use git url
+**Example:**
 
-```powershell
-pwsh /home/azure-sdk-for-net/eng/scripts/automation/Invoke-TypeSpecDataPlaneGenerateSDKPackage.ps1 -sdkFolder /home/azure-sdk-for-net/sdk/anomalyDetector/Azure.AI.AnomalyDetector -typespecSpecDirectory specification/cognitiveservices/AnomalyDetector -commit ac8e06a2ed0fc1c54663c98f12c8a073f8026b90 -repo Azure/azure-rest-api-specs
+```bash
+tsp-client init --tsp-config https://github.com/Azure/azure-rest-api-specs/blob/c226a37cdb9a3f756aff9edb33435ba7c90a5b91/specification/ai/ContentUnderstanding/tspconfig.yaml
 ```
 
-**Note**:
+This will initialize the `tsp-location.yaml` file with the correct configuration. After running this command, you'll still need to create the project structure and files manually.
+
+### Option 2: Copy the Azure.Template project
+
+You can copy the [Azure.Template](https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/template/Azure.Template) project as a starting point. This template includes the complete project structure with:
 
-- `-sdkFolder` take the address of the sdk folder in azure-sdk-for-net repo. e.g. /home/azure-sdk-for-net/sdk/anomalyDetector/Azure.AI.AnomalyDetector. [Required]
-- `-typespecSpecDirectory` takes the relative path of the typespec project folder in spec repo. e.g. specification/cognitiveservices/AnomalyDetector [Required]
-- `-additionalSubDirectories` takes the relative paths of the additional directories needed by the typespec project, such as share library folder, separated by semicolon if there is more than one folder. [Optional]
-- `-commit` takes the git commit hash  (e.g. ac8e06a2ed0fc1c54663c98f12c8a073f8026b90) [Required]
-- `-repo` takes the `<owner>/<repo>` of the REST API specification repository. (e.g. Azure/azure-rest-api-specs), [Optional], default is `Azure/azure-rest-api-specs`
+- Project files (`.csproj`, `.sln`)
+- TypeSpec configuration (`tsp-location.yaml`)
+- Test infrastructure
+- Sample structure
+- CI/CD configuration
 
-When you run `eng\scripts\automation\Invoke-TypeSpecDataPlaneGenerateSDKPackage.ps1`, it will:
+**Steps:**
+1. Copy the `sdk/template/Azure.Template` directory to your new location `sdk/<service name>/<package name>/`
+2. Rename the project files and namespaces to match your service
+3. Update the `tsp-location.yaml` file to point to your TypeSpec specification
+4. Update the package name, version, and other metadata in the `.csproj` file
 
-- Create a project folder, install template files from `sdk/template/Azure.Template`, and create `.csproj` and `.sln` files for your new library.
+These files are created following the guidance for the [Azure SDK Repository Structure](https://github.com/Azure/azure-sdk/blob/master/docs/policies/repostructure.md).
 
-    These files are created following the guidance for the [Azure SDK Repository Structure](https://github.com/Azure/azure-sdk/blob/master/docs/policies/repostructure.md).
+For more information on code generation, see the [Azure SDK Code Generation Quickstart Tutorial](https://github.com/Azure/azure-sdk-for-net/blob/main/doc/DataPlaneCodeGeneration/AzureSDKCodeGeneration_DataPlane_Quickstart.md).

doc/GeneratorMigration/Library_Inventory.md

@@ -12,23 +12,23 @@
 
 ## Summary
 
-- Total libraries: 395
-- Management Plane (MPG): 226
-  - Autorest/Swagger: 160
-  - New Emitter (TypeSpec): 24
-  - Old TypeSpec: 42
+- Total libraries: 394
+- Management Plane (MPG): 225
+  - Autorest/Swagger: 159
+  - New Emitter (TypeSpec): 25
+  - Old TypeSpec: 41
 - Data Plane (DPG): 169
-  - Autorest/Swagger: 87
-  - New Emitter (TypeSpec): 16
-  - Old TypeSpec: 17
+  - Autorest/Swagger: 86
+  - New Emitter (TypeSpec): 18
+  - Old TypeSpec: 16
 - No generator: 49
 
 
 ## Data Plane Libraries (DPG) - Migrated to New Emitter
 
 Libraries that provide client APIs for Azure services and have been migrated to the new TypeSpec emitter.
 
-**Migration Status**: 16 / 32 (50%)
+**Migration Status**: 18 / 34 (52.9%)
 
 | Service | Library | New Emitter |
 | ------- | ------- | ----------- |
@@ -54,21 +54,23 @@ Libraries that provide client APIs for Azure services and have been migrated to
 | eventgrid | Azure.Messaging.EventGrid.SystemEvents | ✅ |
 | healthdataaiservices | Azure.Health.Deidentification | ✅ |
 | keyvault | Azure.Security.KeyVault.Administration | ✅ |
-| loadtestservice | Azure.Developer.LoadTesting |  |
+| loadtestservice | Azure.Developer.LoadTesting | ✅ |
 | monitor | Azure.Monitor.Ingestion | ✅ |
 | monitor | Azure.Monitor.Query.Logs | ✅ |
 | monitor | Azure.Monitor.Query.Metrics | ✅ |
 | onlineexperimentation | Azure.Analytics.OnlineExperimentation |  |
+| openai | Azure.AI.OpenAI | ✅ |
 | purview | Azure.Analytics.Purview.DataMap |  |
 | schemaregistry | Azure.Data.SchemaRegistry | ✅ |
+| template | Azure.Template | ✅ |
 | translation | Azure.AI.Translation.Document |  |
 | translation | Azure.AI.Translation.Text | ✅ |
 | vision | Azure.AI.Vision.ImageAnalysis | ✅ |
 
 
 ## Data Plane Libraries (DPG) - Still on Swagger
 
-Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 87
+Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 86
 
 | Service | Library |
 | ------- | ------- |
@@ -153,7 +155,6 @@ Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 87
 | synapse | Azure.Analytics.Synapse.Monitoring |
 | synapse | Azure.Analytics.Synapse.Spark |
 | tables | Azure.Data.Tables |
-| template | Azure.Template |
 | textanalytics | Azure.AI.TextAnalytics |
 | textanalytics | Azure.AI.TextAnalytics.Legacy.Shared |
 | timeseriesinsights | Azure.IoT.TimeSeriesInsights |
@@ -165,7 +166,7 @@ Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 87
 
 Libraries that provide resource management APIs for Azure services and have been migrated to the new TypeSpec emitter.
 
-**Migration Status**: 24 / 66 (36.4%)
+**Migration Status**: 25 / 66 (37.9%)
 
 | Service | Library | New Emitter |
 | ------- | ------- | ----------- |
@@ -181,7 +182,7 @@ Libraries that provide resource management APIs for Azure services and have been
 | computerecommender | Azure.ResourceManager.Compute.Recommender | ✅ |
 | computeschedule | Azure.ResourceManager.ComputeSchedule |  |
 | connectedcache | Azure.ResourceManager.ConnectedCache | ✅ |
-| containerorchestratorruntime | Azure.ResourceManager.ContainerOrchestratorRuntime |  |
+| containerorchestratorruntime | Azure.ResourceManager.ContainerOrchestratorRuntime | ✅ |
 | databasewatcher | Azure.ResourceManager.DatabaseWatcher | ✅ |
 | databox | Azure.ResourceManager.DataBox |  |
 | dellstorage | Azure.ResourceManager.Dell.Storage | ✅ |
@@ -239,7 +240,7 @@ Libraries that provide resource management APIs for Azure services and have been
 
 ## Management Plane Libraries (MPG) - Still on Swagger
 
-Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 160
+Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 159
 
 | Service | Library |
 | ------- | ------- |
@@ -312,7 +313,6 @@ Libraries that have not yet been migrated to the new TypeSpec emitter. Total: 16
 | graphservices | Azure.ResourceManager.GraphServices |
 | guestconfiguration | Azure.ResourceManager.GuestConfiguration |
 | hdinsight | Azure.ResourceManager.HDInsight |
-| hdinsightcontainers | Azure.ResourceManager.HDInsight.Containers |
 | healthbot | Azure.ResourceManager.HealthBot |
 | healthcareapis | Azure.ResourceManager.HealthcareApis |
 | hybridaks | Azure.ResourceManager.HybridContainerService |

doc/GeneratorMigration/Library_Inventory.ps1

@@ -178,9 +178,9 @@ function New-MarkdownReport {
     $dataNewEmitter = $dataLibraries | Where-Object { $_.generator -notin @("Swagger", "TSP-Old", "No Generator") }
     $dataTspOld = $dataLibraries | Where-Object { $_.generator -eq "TSP-Old" }
 
-    # Calculate TypeSpec library counts (only those with tsp-location.yaml)
+    # Calculate TypeSpec library counts (only those with tsp-location.yaml or Azure.AI.OpenAI with special handling)
     $mgmtTypeSpecLibs = $mgmtLibraries | Where-Object { $_.hasTspLocation -eq $true }
-    $dataTypeSpecLibs = $dataLibraries | Where-Object { $_.hasTspLocation -eq $true }
+    $dataTypeSpecLibs = $dataLibraries | Where-Object { $_.hasTspLocation -eq $true -or $_.library -eq "Azure.AI.OpenAI" }
 
     # Calculate migration percentages (migrated / total TypeSpec libraries)
     $mgmtMigrated = $mgmtNewEmitter.Count
@@ -223,8 +223,8 @@ function New-MarkdownReport {
     $report += "**Migration Status**: $dataMigrated / $dataTypeSpecTotal ($dataPercentage%)`n"
     $report += "| Service | Library | New Emitter |"
     $report += "| ------- | ------- | ----------- |"
-    # Only include libraries that have tsp-location.yaml
-    $sortedDataLibs = $dataLibraries | Where-Object { $_.hasTspLocation -eq $true } | Sort-Object service, library
+    # Only include libraries that have tsp-location.yaml or are Azure.AI.OpenAI (special case with hardcoded handling)
+    $sortedDataLibs = $dataLibraries | Where-Object { $_.hasTspLocation -eq $true -or $_.library -eq "Azure.AI.OpenAI" } | Sort-Object service, library
     foreach ($lib in $sortedDataLibs) {
         $newEmitter = if ($lib.generator -notin @("Swagger", "TSP-Old", "No Generator")) { "✅" } else { "" }
         $report += "| $($lib.service) | $($lib.library) | $newEmitter |"