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

Compare Java SDK for compute TypeSpec migration #43116

Open
live1206 opened this issue Nov 27, 2024 · 1 comment
Open

Compare Java SDK for compute TypeSpec migration #43116

live1206 opened this issue Nov 27, 2024 · 1 comment
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Compute Mgmt - Track 2 needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team

Comments

@live1206
Copy link
Member

We are working on the compute TypeSpec migration.
Would like Java to verify the SDK generation of the corresponding swagger of the converted TypeSpec.
We have split compute into multiple sub services and done the conversion for each of them.

For instance, Compute sub-service:

Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amjads1 @avirishuv @Drewm3 @Vaibhav-Agar.

@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Compute needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 27, 2024
@XiaofeiCao XiaofeiCao self-assigned this Nov 27, 2024
@XiaofeiCao XiaofeiCao removed the Service Attention Workflow: This issue is responsible by Azure service team. label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. Compute Mgmt - Track 2 needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team
Projects
None yet
Development

No branches or pull requests

2 participants