https://github.com/markcowl/azure-rest-api-specs/blob/9a31e08d1e35be8d412c0820e1b334f9700c4033/specification/network/resource-manager/Microsoft.Network/Network/Network/VmssNetworkInterface.tsp#L56
Per the previous discussion, we have agreed on a long-term resolution for the VMSS APIs. This tracks option 1, in which the api types returned by VMSS APIs continue to evolve with each new Network version, but the api-version sent with the VMSS API operations stays fixed at 2018-10-01. This will involve a slight reorganization of the network spec, and a return to the layout of the VMSS OpenAPI files from before the TypeSpec conversion. This will require a change in how TypeSpec SDK emitters handle the api-version, as outlined here: https://github.com/markcowl/typespec-azure/blob/markcowl/child-client-api-version-design/docs/child-client-api-version-design.md
The TypeSpec changes and emitter support are targeted for the September release (9/9/26).
https://github.com/markcowl/azure-rest-api-specs/blob/9a31e08d1e35be8d412c0820e1b334f9700c4033/specification/network/resource-manager/Microsoft.Network/Network/Network/VmssNetworkInterface.tsp#L56
Per the previous discussion, we have agreed on a long-term resolution for the VMSS APIs. This tracks option 1, in which the api types returned by VMSS APIs continue to evolve with each new Network version, but the api-version sent with the VMSS API operations stays fixed at 2018-10-01. This will involve a slight reorganization of the network spec, and a return to the layout of the VMSS OpenAPI files from before the TypeSpec conversion. This will require a change in how TypeSpec SDK emitters handle the api-version, as outlined here: https://github.com/markcowl/typespec-azure/blob/markcowl/child-client-api-version-design/docs/child-client-api-version-design.md
The TypeSpec changes and emitter support are targeted for the September release (9/9/26).