Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-11-15-preview Congitive Services/Language-Authoring updates #31127

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

PranshuBansalDev
Copy link
Member

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.

PR review workflow diagram

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

spec_pr_review_workflow_diagram

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.

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

Tooling

Guidelines & Specifications

Helpful Links

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.

Copy link

openapi-pipeline-app bot commented Oct 21, 2024

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR has at least one change violating Azure versioning policy (label: VersioningReviewRequired).
    To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch.
  • ❌ The required check named Swagger BreakingChange has failed. To unblock this PR, follow the process at aka.ms/brch.

Copy link

openapi-pipeline-app bot commented Oct 21, 2024

@PranshuBansalDev PranshuBansalDev changed the title v1 typspec commit 2024-11-15-preview Congitive Services/Language-Authoring updates Oct 21, 2024
@AzureRestAPISpecReview AzureRestAPISpecReview added BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required data-plane new-api-version TypeSpec Authored with TypeSpec labels Oct 21, 2024
@PranshuBansalDev PranshuBansalDev added the PublishToCustomers Acknowledgement the changes will be published to Azure customers. label Oct 21, 2024
@JeffreyRichter JeffreyRichter added the BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior label Oct 22, 2024
…ations and Including Test JSON (#3)

* - added the additional apis of ExportedModelController to version 2024-11-15-preview
- compiled

* - added testing jsons for newly added api from ExportedModelController
- compiled
Copy link

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

@AzureRestAPISpecReview AzureRestAPISpecReview added VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required and removed new-api-version BreakingChangeReviewRequired <valid label in PR review process>add this label when breaking change review is required BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior labels Oct 24, 2024
Copy link
Member

@markcowl markcowl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please set emit-lro-options: "all" in your tspconfig.yaml so we can see the lro properties of your new operations in swagger. Also there is a non-standard PUT that needs review board approval, and soem suggestions for simplifying the naming.

*/
@added(Versions.v2024_11_15_preview)
@clientName("DataGenerationConnectionInfo")
model TextAnalysisAuthoringDataGenerationConnectionInfo {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just call this model DataGenerationConnectionInfo?

*/
@added(Versions.v2024_11_15_preview)
@clientName("DataGenerationSettings")
model TextAnalysisAuthoringDataGenerationSettings {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just call this DataGenerationSettings?

@clientName("ExportedTrainedModel", "csharp")
@resource("exported-models")
@parentResource(ConversationalAnalysisAuthoringProjectMetadata)
model ConversationalAnalysisAuthoringExportedTrainedModel {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just call this ExportedTrainedModel?

@clientName("ExportedModelJobState", "csharp")
@resource("jobs")
@parentResource(ConversationalAnalysisAuthoringExportedTrainedModel)
model ConversationalAnalysisAuthoringExportedModelJobState {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, why not simplify the name to mattch the client name?

*/
@clientName("ExportedModelOptions")
@added(Versions.v2024_11_15_preview)
model ConversationalAnalysisAuthoringExportedModelOptions {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment on name simplification

@delete
@pollingOperation(ConversationalAnalysisAuthoring.getExportedModelJobStatus)
@added(Versions.v2024_11_15_preview)
deleteExportedModel is Foundations.LongRunningOperation<
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this custom operation needed?

@path
exportedModelName: string;
},
AcceptedResponse,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to include standard headers like Operation-Location

@put
@pollingOperation(ConversationalAnalysisAuthoring.getExportedModelJobStatus)
@added(Versions.v2024_11_15_preview)
createOrUpdateExportedModel is Foundations.LongRunningOperation<
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This violates the guidelines for LRO PUT operations, has this been approved by the API review Board?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cognitive Services data-plane PublishToCustomers Acknowledgement the changes will be published to Azure customers. TypeSpec Authored with TypeSpec VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Language Customization - Custom NER and Custom text classification (CT)] API Review
5 participants