Compute: costs values is not returned for ResourceSKU

[yaohaizh]

There is field defined in the swagger spec for sku's costs: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/Microsoft.Compute/stable/2019-04-01/skus.json, but can not find this values from the service return responses.
Related issue:
Azure/azure-libraries-for-net#718

[mjconnection]

Hey thanks for reporting this issue. We are sending this to the correct team to do some additional research.

@hyonholee - Spoke to @Drewm3 and he will be looking into this issue.

[Drewm3]

This is by design. There are a set of standard SKU definitions in the swagger, but only though documented here for compute are supported today: [https://docs.microsoft.com/en-us/rest/api/compute/resourceskus/list]

[yaohaizh]

Just wonder should the swagger spec need change to reflect this design?

[qub1n]

I see different version in API:

2019-04-01
in https://github.com/Azure/azure-rest-api-specs/blob/master/specification/compute/resource-manager/Microsoft.Compute/stable/2019-04-01/skus.json

but
2017-09-01 in https://docs.microsoft.com/en-us/rest/api/compute/resourceskus/list

Isn't this the root cause?

[qub1n]

This is by design. There are a set of standard SKU definitions in the swagger, but only though documented here for compute are supported today: [https://docs.microsoft.com/en-us/rest/api/compute/resourceskus/list]

Why this desing?

azure-libraries-for-net team does not want to add support for Cost API without having it in swagger.
On the other hand it is by design that it is not in swagger?

So what is the correct approach to accessing the Costs?

[Drewm3]

The reason for the current design is the fact that there is not a commerce provided API to get the cost of a specific type of resource that is available consistently through all channels of Azure customers. For example there is an API that works for Azure customers who have signed up through the Azure Portal, but that API does not work for Azure customers who are paying through a mechanism called an Enterprise Agreement. Within Azure VMs we are willing to change this design if/when there is a consistent way for us to provide a reference which all customers can use to get the price of the VM size, but we are unable to provide multiple configuration details for the multiple different methods required to get the price of a resource today.

[qub1n]

ok, thanks for explaining.