[Cogs Face] Align with latest released version of Face API with feature of multiple recognition models. #5381
Conversation
…to spaces, Add new definitions named MetaDataContract inheriting from NameAndUserDataContract
…ing format issue.
… from 'path' to 'query'
…gnitionModel description.
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
|
@johan can help explain more on this and I would appreciate if you could kindly offer us a sign-off from Azure API review's perspective, thanks. |
Automation for azure-sdk-for-nodeA PR has been created for you: |
@veronicagg Thanks a lot for your quick review while our asking for exception to Azure API review is still on-going. Please hold on this a little bit and will let you know when we reach agreement on merging this. |
specification/cognitiveservices/data-plane/Face/stable/v1.0/Face.json
Outdated
Show resolved
Hide resolved
specification/cognitiveservices/data-plane/Face/stable/v1.0/Face.json
Outdated
Show resolved
Hide resolved
REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit
|
This involves API design changes. Have you finished the API design review? |
|
Hi @yangyuan , could you please first add a Do-Not-Merge label for this PR? Actually we are now asking the API review board for exception and we are also applying some API interface changes for service side now upon the review comments. There will be changes for the Swagger after we finalize the implementation for service side and get review sign-off. Will ping back this PR then. |
REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit
|
@lebronJ would you prefer to close this PR and re-open when you're ready? you can tag me back when ready. Thanks! |
specification/cognitiveservices/data-plane/Face/stable/v1.0/Face.json
Outdated
Show resolved
Hide resolved
REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit
Hi @veronicagg and @yangyuan, we have gotten the API review sign-off and I have forwarded it to Cognitive Services Experience Team and you two. Can we move forward to review and merge this as soon as possible (thanks), so that we can catch the dates of our roll out, along with the API reference updates, SDKs and samples? |
Besides, could anyone please help remove the DoNotMerge label and reopen the PR of SDK changes? Let me know if any action needed from my side. |
veronicagg
left a comment
There was a problem hiding this comment.
Based on the above, the specs submitted reflect your APIs which have been deployed, so I'm approving and merging. To request SDKs releases, please use https://portal.azure-devex-tools.com/app/tools/request-api-release . Thanks!
* .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit
|
@AutorestCI regenerate azure-sdk-for-go |
* .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit * .NET SDK Resource Provider:'Face' REST Spec PR 'Azure/azure-rest-api-specs#5381' REST Spec PR Author 'lebronJ' REST Spec PR Last commit
(I am one of the main devs working on Face API and Face containers.)
This is to align Face API swaggers with latest published version with Multiple Recognition Model features. (rollout will be started as soon as we get final approval from API review side)
Note: This PR has
I understand this will be a breaking change from SDK perspective while at least this will not affect existing SDK users before they upgrade to latest SDK version. We have asked an exception from Azure API Review Board for this.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.