New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cost Management] [API Management] Azure Cost Management Package just throws first 1000 lines and not managing the paging from the cost management rest api #23175
Comments
Label prediction was below confidence level |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ccmixpdevs. Issue Details
Describe the bug To Reproduce
Expected behavior Screenshots Additional context
|
Thanks @victorsalesa, you're correct - it does not look like this operation has been identified as pageable in the specification that is used to generate the SDK: I have tagged the Cost Management team to hopefully get this resolved ASAP :) |
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ccmixpdevs. Issue Details
Describe the bug To Reproduce
Expected behavior Screenshots Additional context
|
Sorry for the inconvenience. but we have a backlog item to fix this issue. |
Hi @omrodrig . Am I able to access that backlog item to track the issue status?. Could you please provide a link? |
Hi @victorsalesa , python SDK is generated with swagger. Just like #23175 (comment), swagger doesn't define the operation as pageable so SDK will not treat it as pageable. If you want the feature, it is better to make issue in https://github.com/Azure/azure-rest-api-specs/issues. Thanks! |
Hi @victorsalesa. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “ |
Hi @victorsalesa, since you haven’t asked that we “ |
Sorry, i'm having the same problem, but from the thread i don't understand if the issue will be fixed or not. Thanks in advance for your help. In the meantime did you find some workaround ? |
@sgiovetti I was the one notificating that and copying that. It seems that the python api is generated with azurerest tool. I guess that it will be simply changing the swagger definition for the next release to include the iteration capability but no answer yet |
Hi folks - was this issue ever resolved? If so, what package version is it fixed on? |
Describe the bug
When you call the Usage method in python: https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/costmanagement/azure-mgmt-costmanagement/azure/mgmt/costmanagement/operations/_query_operations.py
that is related to this REST api endpoint here https://docs.microsoft.com/es-es/rest/api/cost-management/query/usage
the python api is not looping to get next page using the nextLink attribute in the response described here https://docs.microsoft.com/es-es/rest/api/cost-management/query/usage#queryresult
so we get a 1000 rows maximum per execution and no way to manage the paging with this library
To Reproduce
Expected behavior
As a python developer using this package I would expect the result to be an iterable so I can get all result pages not just the first one
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: