HealthDataAIServices Deidentificiation Data Plane - GA Stable API Changes#30518
HealthDataAIServices Deidentificiation Data Plane - GA Stable API Changes#30518GrahamMThomas merged 71 commits intoAzure:mainfrom GrahamMThomas:healthdataaiservices/customization-options
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Generated ApiView
|
…github.com/GrahamMThomas/azure-rest-api-specs into healthdataaiservices/customization-options
…github.com/GrahamMThomas/azure-rest-api-specs into healthdataaiservices/customization-options
There was a problem hiding this comment.
I wasn't in the review meeting. If any of my feedback is already resolved there, feel free to "resolve" that comment.
I didn't see response to review meeting feedback of #30515 (comment)
I'd expect a simple response to it (e.g. which item is resolved, which is not).
specification/healthdataaiservices/HealthDataAIServices.DeidServices/models.tsp
Show resolved
Hide resolved
specification/healthdataaiservices/HealthDataAIServices.DeidServices/routes.tsp
Show resolved
Hide resolved
specification/healthdataaiservices/HealthDataAIServices.DeidServices/models_document_flow.tsp
Outdated
Show resolved
Hide resolved
specification/healthdataaiservices/HealthDataAIServices.DeidServices/models_document_flow.tsp
Show resolved
Hide resolved
specification/healthdataaiservices/HealthDataAIServices.DeidServices/models_document_flow.tsp
Show resolved
Hide resolved
|
API change check APIView has identified API level changes in this PR and created following API reviews. HealthDataAIServices.DeidServices-HealthDataAIServices.DeidServices |
I've added TODOs for the customizationOptions doc link as we don't have the docs built yet. Regarding the "Recommend looking at Document Translator for naming consistency", do you remember what specifically which models we were trying to sync? |
I went a recap of the meeting. I think the "naming consistency" is about the name of PS: ideally, during SDK review, the changes would be limited to the customization within client.tsp (rename, restructure the clients, etc.), which only need SDK dev approval. |
weidongxu-microsoft
left a comment
There was a problem hiding this comment.
LGTM.
A few minor comments, but no major problem to me.
specification/healthdataaiservices/HealthDataAIServices.DeidServices/models_document_flow.tsp
Show resolved
Hide resolved
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
SDK automation for Java is expected to fail, as the customization is not yet in Java SDK repo |
…om:GrahamMThomas/azure-rest-api-specs into healthdataaiservices/customization-options
| "schema": { | ||
| "$ref": "#/definitions/Azure.Core.Foundations.ErrorResponse" | ||
| }, | ||
| "headers": { |
There was a problem hiding this comment.
You probably want the x-ms-client-request-id defined for error responses as well -- that's where it is really needed. This is a bug in TypeSpec and there is already an open issue for it:
https://github.com/Azure/typespec-azure-pr/issues/3427
…nges (Azure#30518) * Adds CustomizationOptions * Regenerates Examples * Model tweaks * Updates examples * Updates after team meeting * Renames customization options * Introduces new version * Revert old version * Fixes pipeline failures * Recompile * Location is no longer a sas uri * Fixes models prettier * Rename variables in csharp only * tsp format * Latest updates from SDK Review * Add OperationType model for realtime * Change Java service name from DeidServices (default) to Deidentification * get*Count() for Java * Rename DeidentificationClient in JS * WIP * Attempt switching to raw operation * Round 2 * Round 3 * Round 4 * Initial examples * Rename to CustomizationOptions * Mark listJobs and listJobDocuments as internal * csharp-specific changes * Add customization for java in tspconfig * npm update * Changes for python * No longer need python method to be internal * Re-ran e2e script * Revert "Merge branch 'main' into healthdataaiservices/customization-options" This reverts commit a355b96, reversing changes made to 3803319. * tsp format * Delete unnecessary files * Reapply "Merge branch 'main' into healthdataaiservices/customization-options" This reverts commit db141b4. * Restore package-lock.json * Remove HTTPS prefix * Rename body to content in C# * Change endpoint from str to url * Typespec validation * Deprecate 2024-07-12 examples; Updates examples * Validation fixes 1 * Prefixes customizationoptions with deidentification * Adds back in old spec * Adds back in old spec to readme.md * REVERT - Adds back in old spec to readme.md * Moving Azure.ClientGenerator.Core to client.tsp * Use clientName in routes.tsp for renaming "body" * Delete specification/healthdataaiservices/HealthDataAIServices.DeidServices/.gitignore * Use ResourceList and alias * e2e with name instead of jobName * Deprecates Partial Failed * Adds todos for doc links * Adds doc link to redaction format * Recompiles * Tsp format * Removes minimum length restriction from prefix to allow whole container prefix --------- Co-authored-by: Graham Thomas <gthomas@microsoft.com> Co-authored-by: Alexa Thomases <athomases@microsoft.com> Co-authored-by: alexathomases <55257302+alexathomases@users.noreply.github.com> Co-authored-by: Mike Soennichsen <msoennichsen@microsoft.com>
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.Goal of this PR is to add a few features we are looking to add in GA. Going from a preview version to GA. Want to make a few breaking changes to the schema before we release our first stable version.
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.
Is this review for (select one):
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.
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 ApiViewcomment 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.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links
Getting help
write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.