-
Notifications
You must be signed in to change notification settings - Fork 5k
[Core] Wiring up rehydration token logic in data-plane #49224
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
Conversation
API Change CheckAPIView identified API level changes in this PR and created the following API reviews Azure.AI.FormRecognizer |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me, but I'll ask that @JoshLove-msft and @m-nash be the authoritative approvals here, as there are generator and management plane implications.
sdk/core/Azure.Core/src/Shared/NextLinkOperationImplementation.cs
Outdated
Show resolved
Hide resolved
sdk/core/Azure.Core/src/Shared/NextLinkOperationImplementation.cs
Outdated
Show resolved
Hide resolved
sdk/core/Azure.Core/src/Shared/NextLinkOperationImplementation.cs
Outdated
Show resolved
Hide resolved
sdk/keyvault/Azure.Security.KeyVault.Certificates/src/DeleteCertificateOperation.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keyvault and confidential ledger LGTM
API change check API changes are not detected in this pull request. |
Currently DPG libraries do not support rehydrating long-running operations. This means that, after a long-running operation has been started, users must hold their
Operation<T>
reference until its completion in order to access its final result. This can be a problem as some operations could take hours or even days to complete.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 had not been wired into our
Operation
API yet.Fixes #48594.