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

[FEATURE REQ] Ability to track database import progress: return operation id from import action #31607

Closed
tbolon opened this issue Oct 5, 2022 · 4 comments
Assignees
Labels
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. 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 SQL

Comments

@tbolon
Copy link

tbolon commented Oct 5, 2022

Library name

Azure.ResourceManager.Sql

Please describe the feature.

When running a database import operation SqlDatabaseResource.Import() with Azure.WaitUntil.Started we have no details about the started operation. The json returned by the response does not contains data about the operation id: {"operation":"Import","startTime":"2022-10-05T15:25:48.9506752Z"}.

We can't obtain the operation id, since the Id property throw a NotImplementedException.

When calling UpdateStatus method, the json returned contains the operation id: {"name":"f2d498c4-2f32-44e2-bca9-3f41bf29f59f","status":"InProgress","startTime":"2022-10-05T15:25:48Z"}.

I would like to use SqlDatabaseResource.GetDatabaseOperations() to track the import progress, but the only way is to manually parse the json after the UpdateStatus() to obtain the operation id.

Could the ArmOperation<ImportExportOperationResult> expose the operation id when calling Import with Azure.WaitUntil.Started ?

@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 Oct 5, 2022
@azure-sdk
Copy link
Collaborator

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Cognitive Services:0.0881831,Communication:0.063342765,ARM:0.052724548'

@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 and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Oct 5, 2022
@jsquire
Copy link
Member

jsquire commented Oct 5, 2022

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

@xboxeer
Copy link

xboxeer commented Oct 9, 2022

@tbolon Similar issue here #31549 , we are working on a new feature to fix this Azure/autorest.csharp#2158
CC: @ArthurMa1978 @m-nash

If you have any other feedback regarding our Azure SDK, feel free to let us know in this survey

@fengzhou-msft fengzhou-msft self-assigned this Feb 7, 2023
@ArthurMa1978 ArthurMa1978 added 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 labels May 22, 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 Nov 7, 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. feature-request This issue requires a new behavior in the product in order be resolved. 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 SQL
Projects
None yet
Development

No branches or pull requests

6 participants