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

Adding Operations and Enable CSharp SDK Generation for Workloads #31675

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

Conversation

jaskisin
Copy link
Contributor

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.

Jaskirat Singh and others added 30 commits September 16, 2024 19:43
@AzureRestAPISpecReview AzureRestAPISpecReview added NotReadyForARMReview VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required and removed BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior labels Nov 27, 2024
@jaskisin jaskisin added BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior and removed VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required NotReadyForARMReview labels Nov 27, 2024
@AzureRestAPISpecReview AzureRestAPISpecReview added NotReadyForARMReview VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required and removed BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior labels Nov 29, 2024
@jaskisin jaskisin added BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior and removed VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required NotReadyForARMReview labels Nov 29, 2024
@AzureRestAPISpecReview AzureRestAPISpecReview added NotReadyForARMReview VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required and removed BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior labels Nov 29, 2024
Copy link
Member

@venu-sivanadham venu-sivanadham left a comment

Choose a reason for hiding this comment

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

:shipit:

@jaskisin jaskisin added BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior and removed VersioningReviewRequired <valid label in PR review process>add this label when versioning review is required NotReadyForARMReview labels Nov 29, 2024
@jaskisin
Copy link
Contributor Author

jaskisin commented Nov 29, 2024

For dotnet, we need to create new directory as service has split the swagger/typespec at RT level, this will be done separately to dotnet sdk repo.

@pratikjoshi14 pratikjoshi14 added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMReview ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review AzCoreIDC BreakingChange-Approved-BugFix Changes are to correct the REST API definition to correctly describe service behavior BreakingChange-Go-Sdk BreakingChange-Go-Sdk-Approved ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager RPaaS TypeSpec Authored with TypeSpec
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants