Compare Java SDK for compute TypeSpec migration

[live1206]

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:

• https://github.com/Azure/azure-rest-api-specs/blob/feature/cplat-typespecTest/specification/compute/Compute.Management/readme.md is the readme containing input files of original swaggers.
• https://github.com/Azure/azure-rest-api-specs/blob/feature/cplat-typespecTest/specification/compute/Compute.Management contains the converted TypeSpec, we need to compile them firstly to get the corresponding swgger then generate SDK
• Get diff from the generated SDK from original swagger and new swagger

[github-actions]

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

[XiaofeiCao]

Current major issue is that some of the LIST operations are not generated with pageable, e.g.
https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L1582

Original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/computeRPCommon.json#L171-L173

Majority of the compilation issues are caused by this.

[pshao25]

Current major issue is that some of the LIST operations are not generated with pageable, e.g. https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L1582

Original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/computeRPCommon.json#L171-L173

Majority of the compilation issues are caused by this.

Could you give me a complete list for this?

[XiaofeiCao]

Compilation issues

1. LIST without pageable

• VirtualMachineSizes_List
• AvailabilitySets_ListAvailableSizes
• DedicatedHosts_ListAvailableSizes
• VirtualMachines_ListAvailableSizes

2. VirtualMachineScaleSetExtension without settable name property

Though there's PUT operation for VirtualMachineScaleSetExtension, we can still create one within VitualMachineScaleSet. Thus name property should be included as well.
(name property in common model ProxyResource is read-only and not settable)
current swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/a5f4c22d62eecd7f15f2434d0fca00dc3589b01d/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/ComputeRP.json#L19009-L19027
original swagger: https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/virtualMachineScaleSet.json#L4479-L4481
(Current Java codegen still has issue even if it's added, could be azure-json issue. Though name should be there anyway.)

3. No AvailabilitySetSkuType model

This seems an orphan model, though Java still uses it in handwritten code. Not sure if other languages use it.
https://github.com/XiaofeiCao/azure-rest-api-specs/blob/typespec_compute/specification/compute/resource-manager/Microsoft.Compute/ComputeRP/stable/2024-07-01/availabilitySet.json#L490

[XiaofeiCao]

@pshao25 I've compiled a complete list of current swagger issues that generate compilation errors for Java.

I've yet to run tests and generate apiviews. Will update above list once those are done.