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

[Core] Data-plane: enable LRO rehydration #48594

Open
kinelski opened this issue Mar 6, 2025 · 0 comments
Open

[Core] Data-plane: enable LRO rehydration #48594

kinelski opened this issue Mar 6, 2025 · 0 comments
Assignees
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Milestone

Comments

@kinelski
Copy link
Member

kinelski commented Mar 6, 2025

Our TypeSpec code generator already supports the creation of rehydration tokens to retrieve the status of long-running operations, but the logic to do so has not been wired into our Operation API yet. Once this issue is addressed, the following piece of code is expected to work when rehydrating an operation with return value T:

// Store the rehydration token for later.
RehydrationToken token = operation.GetRehydrationToken().Value;

// Restore the operation with the rehydration token.
Operation<T> operation = Operation.Rehydrate<T>(client.Pipeline, token);
@kinelski kinelski self-assigned this Mar 6, 2025
@kinelski kinelski added Client This issue points to a problem in the data-plane of the library. Azure.Core labels Mar 6, 2025
@github-actions github-actions bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 6, 2025
@kinelski kinelski removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Mar 6, 2025
@kinelski kinelski added this to the 2025-04 milestone Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core Client This issue points to a problem in the data-plane of the library.
Projects
None yet
Development

No branches or pull requests

1 participant