Microsoft.CostManagement swagger incorrect

[jazelenk]

https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2019-11-01/costmanagement.json

QueryDatasetConfiguration shows a "columns" option. The Microsoft.CostManagement team says that no such option exists. Indeed, attempting to use it fails.

https://github.com/Azure/azure-rest-api-specs/tree/master/specification/cost-management/resource-manager/Microsoft.CostManagement/stable shows API versions 2020-06-01 and 2021-01-01. Those versions are not recognized by the RP, and the team confirmed that they are not valid. I believe this is the root cause of Azure/azure-sdk-for-python#16102 - some autorest-like thing sees those versions and attempts to use them as defaults because they are newer and published in -stable.

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ms-premp, @ramaganesan-rg.

Issue Details

---

https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2019-11-01/costmanagement.json

QueryDatasetConfiguration shows a "columns" option. The Microsoft.CostManagement team says that no such option exists. Indeed, attempting to use it fails.

https://github.com/Azure/azure-rest-api-specs/tree/master/specification/cost-management/resource-manager/Microsoft.CostManagement/stable shows API versions 2020-06-01 and 2021-01-01. Those versions are not recognized by the RP, and the team confirmed that they are not valid. I believe this is the root cause of Azure/azure-sdk-for-python#16102 - some autorest-like thing sees those versions and attempts to use them as defaults because they are newer and published in -stable.

Author:	jazelenk
Assignees:	leni-msft
Labels:	Cost Management, Service Attention, needs-triage
Milestone:	-

[jochav]

Hi there, we are looking into it right now, thanks for the heads up @jazelenk

[omrodrig]

For the first issue regarding the "columns" field. The document is misleading. "Columns" is not a field used in the request. This field is used in the response. I will update the documentation accordingly. With regards to the second issue regarding 2020-06-01 and 2020-01-01 not recognizing the RP Query, this will be resolved with our newest version 2020-10-01. Which has already been deployed recently.