Azure / Azure/azure-rest-api-specs
Cost Management] [API Management] Azure Cost Management Package just throws first 1000 lines and not managing the paging from the cost management rest api
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 432
Description
As per described in https://github.com/Azure/azure-sdk-for-python/issues/23175 it seems that the query endpoint https://docs.microsoft.com/es-es/rest/api/cost-management/query/usage in the cost management api spec is not described as pageable in the swagger definition https://github.com/Azure/azure-rest-api-specs/blob/main/specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2021-10-01/costmanagement.json#L950 what makes the python api method here
https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/costmanagement/azure-mgmt-costmanagement/azure/mgmt/costmanagement/operations/_query_operations.py
not able to retrieve all the results for a specific query.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the pageable definition around line 950 of specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2021-10-01/costmanagement.json and compare the behavior described in issue 23175. Then inspect the generated _query_operations.py implementation in the Python SDK. Done means the query endpoint's specification and generated client can retrieve results beyond the first 1,000 lines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- openapi, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100