Add AI Face next GA version

[Han-msft]

Data Plane API Specification Update Pull Request

Tip

Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

• Add new api version for face
  • Exclude Person Directory, which is not ready for GA.

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics

Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

• Link to API Spec engagement record issue:

Is this review for (select one):

• a private preview
• a public preview
• GA release

Change Scope

^{This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.}

• Design Document:
• Previous API Spec Doc:
• Updated paths:

Viewing API changes

For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.

❔Got questions? Need additional info?? We are here to help!

Contact us!

The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

• 💬 Teams Channel
• 💌 email

Click here for links to tools, specs, guidelines & other good stuff

Tooling

• Open API validation tools were run on this PR. Go here to see how to fix errors
• Spectral Linting

Guidelines & Specifications

• Azure REST API Guidelines
• OpenAPI Style Guidelines
• Azure Breaking Change Policy

Helpful Links

• Schedule a data plane REST API spec review

Getting help

• First, please carefully read through this PR description, from top to bottom.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
  and https://aka.ms/ci-fix.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
  This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

fix #31108

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This is the public specs repo main branch which is not intended for iterative development.
  You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
  If this is what you intend, add PublishToCustomers label to your PR.
  Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ Your PR requires an API stewardship board review as it introduces a new API version (label: new-api-version). Schedule the review by following aka.ms/azsdk/onboarding/restapischedule.
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. 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. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app]

Generated ApiView

Language	Package Name	ApiView Link
.Net	Azure.AI.Vision.Face	https://apiview.dev/Assemblies/Review/eb53e084ca214df6ad3917783dfac80c?revisionId=901ab6fbfdd64eb1a321409273a4030e
Java	azure-ai-vision-face	https://apiview.dev/Assemblies/Review/572978f1cf2945df8bcf83aa83876685?revisionId=4d267ea193be4963bcd80b8bb8cc33fb
Python	azure-ai-vision-face	https://apiview.dev/Assemblies/Review/902546534b9f40729eabfbd725b02bff?revisionId=1bf9c955830349138fc7ed0704e74f46
Swagger	Face	https://apiview.dev/Assemblies/Review/2ab42e93e3c64f34aa8dfb69ea93cf15?revisionId=aae3ac1d0b2144f29f24d9a45198aeac
Swagger	v1.2	https://apiview.dev/Assemblies/Review/f384260bab8c4808bd26312750e8f04a?revisionId=29c0e594da764ea6a7e0cb6322fb4151
TypeSpec	Face	https://apiview.dev/Assemblies/Review/fd70378562b9470abec3d3f5e04aa38f?revisionId=4e660386a95b490da2e24618cf8b4aa0

[mikekistler]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[mikekistler]

Breaking changes previously reviewed and approved in #29781

[mikekistler]

Looks good. 👍

[weidongxu-microsoft]

Please double check that the API and model of these not-to-be-GAed-in-v1.2 interface/operation does not appear in Swagger.

[Han-msft]

Looks fine, might because omit-unreachable-types: true in tspconfig.yaml

[allenjzhang]

This is a retro breaking change. Shouldn't you use @rename versioning decorator?

[Han-msft]

I thought it's okay since it's mostly only affecting documentation. We are not changing the actual name inside payload.
BTW, this is some feedback from C# SDK review, but I think it worth to change it at REST level for better naming.