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.

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

[QUERY] How to create a long running polling object from uri #31549

Closed
PepijnGramberg opened this issue Sep 30, 2022 · 5 comments
Closed

[QUERY] How to create a long running polling object from uri #31549

PepijnGramberg opened this issue Sep 30, 2022 · 5 comments
Assignees
Labels
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 SQL

Comments

@PepijnGramberg
Copy link

Library name and version

Azure.ResourceManagement.Sql 1.0.0

Query/Question

When using SqlDatabaseResource.ExportAsync(WaitUntil.Started,....) it returns ArmOperation<ImportExportOperationResult> which can be used to update the status periodically to poll whether the export is completed.

However in our architecture, we would like to do the polling from another (distributed) service, the polling object does expose .Id which should give an uri that can be used to poll, but how would that be used in combination with the ArmClient? Or do you have to start doing low level http calls yourself, including dealing with all authentication issues?

This might be a more generic problem/feature for all kinds of long polling situations.

Environment

No response

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Sep 30, 2022
@azure-sdk
Copy link
Collaborator

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'ARM:0.5829653,Azure.Core:0.036238294,Extensions:0.029453533'

@jsquire jsquire added SQL 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 labels Sep 30, 2022
@jsquire
Copy link
Member

jsquire commented Sep 30, 2022

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 30, 2022
@xboxeer
Copy link

xboxeer commented Oct 9, 2022

@PepijnGramberg
We are working on a new feature Azure/autorest.csharp#2158 that will address your concern, right now this is something that our SDK cannot help
CC: @ArthurMa1978 @m-nash , do let me know if there is a workaround on this
If you have any other feedback regarding our Azure SDK, feel free to let us know in this survey

@ArthurMa1978
Copy link
Member

This is a new feature we are working with, currently no workaround, and we planned to ship this feature by the end of this year, maybe next month.

@fengzhou-msft fengzhou-msft self-assigned this Feb 7, 2023
@ArthurMa1978
Copy link
Member

Close this as we have created the Rehydration issue to track this feature.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
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 SQL
Projects
None yet
Development

No branches or pull requests

7 participants