[DNM] Validate typespec-azure#2607

[AlitzelMendez]

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ The required check named spec-gen-sdk - go - pullrequest has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide
• ❌ The required check named Protected Files has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[github-actions]

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language	API Review for Package
Swagger	AnomalyDetector-ContentSafety
Swagger	AnomalyDetector-Language
Swagger	ApiCenter.DataApi
Swagger	Azure.AI.DocumentTranslation-Azure.AI.DocumentTranslation
Swagger	Azure.Analytics.Purview.Account
Swagger	Azure.Batch
Swagger	Azure.Contoso.WidgetManager
Swagger	Azure.Developer.TrustedSigning
Swagger	Azure.ProgrammableConnectivity
Swagger	CallAutomation-JobRouter
Swagger	CallAutomation-Messages
Swagger	HealthDataAIServices.DeidServices-HealthDataAIServices.DeidServices
Swagger	LiveMetrics-LiveMetrics
Swagger	Microsoft.ApiCenter
Swagger	Microsoft.App.DynamicSessions
Swagger	Microsoft.AppConfiguration
Swagger	Microsoft.DevCenter
Swagger	Microsoft.KeyVault
Swagger	Microsoft.LoadTestService
Swagger	Microsoft.MachineLearningServices
Swagger	Microsoft.OnlineExperimentation
Swagger	Microsoft.PlaywrightTesting.AuthManager
Swagger	Microsoft.Quantum
Swagger	Microsoft.SchemaRegistry
Swagger	Microsoft.VoiceServices-Microsoft.VoiceServices
Swagger	Oracle.Database
Swagger	Azure.AI.Agents-ImageAnalysis
Swagger	Microsoft.PlanetaryComputer

[markcowl]

My main question for the instances where @identifiers(#[]) was needed, is about what the json looks like before we added this? Was a diagnostic warning emitted, or were some identifiers values that seemed incorrect emitted?

[markcowl]

What was the behavior without this addition?

[markcowl]

What was the behavior without this?

[markcowl]

Some question (and for the previous)

[AlitzelMendez]

/azp run

[openapi-pipeline-app]

PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts.

[azure-pipelines]

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.