Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support resume for pagers #23795

Open
thomas11 opened this issue Nov 21, 2024 · 2 comments
Open

Support resume for pagers #23795

thomas11 opened this issue Nov 21, 2024 · 2 comments
Labels
Azure.Core customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team needs-team-triage Workflow: This issue needs the team to triage.

Comments

@thomas11
Copy link

It seems that there's no way currently to resume a listing of resources via a pager. This makes it hard to implement asynchronous APIs where a client requests resource listings in chunks, and the service uses the Azure SDK to retrieve the resource list.

Details: armresources.Client and armresources.ResourceGroupsClient, and possibly other clients as well, support listing resources via runtime.Pager. The types returned by the pager, such as ResourceGroupListResult, have a NextLink property. Even though the property is public, it's not used anywhere else except internally. There's no equivalent to NewPollerFromResumeToken that would create a Pager that continues from a given nextLink.

If that's truly not possible, why expose NextLink? I hope it can be added, though.
@github-actions github-actions bot added ARM customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 21, 2024
@github-actions GitHub Actions
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @armleads-azure.

@lirenhe lirenhe removed the Service Attention Workflow: This issue is responsible by Azure service team. label Nov 22, 2024
@github-actions github-actions bot added the needs-team-triage Workflow: This issue needs the team to triage. label Nov 22, 2024
@lirenhe
Copy link
Member

lirenhe commented Nov 22, 2024

@jhendrixMSFT, could you help to triage this ask? I am not sure whether this could be done directly on client side.

@jhendrixMSFT jhendrixMSFT added Azure.Core feature-request This issue requires a new behavior in the product in order be resolved. and removed question The issue doesn't require a change to the product in order to be resolved. Most issues start as that ARM Mgmt This issue is related to a management-plane library. labels Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Azure.Core customer-reported Issues that are reported by GitHub users external to the Azure organization. feature-request This issue requires a new behavior in the product in order be resolved. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team needs-team-triage Workflow: This issue needs the team to triage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@thomas11 @lirenhe @jhendrixMSFT