-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Convert old operation types to use new Operation Helper #22914
Comments
Note: OperationHelper has been superseded by OperationInternal |
Removing this from TA for project tracking purposes since it's already handled. |
@kinelski is this still valid, can you please help me understand what is needed to be done here and what is the benefit of doing this? |
This may be superseded by other LRO efforts happening in Core. If not, we should file a "step back and take stock of LROs and unify the many LRO pieces we have" issue, possibly as part of #28369 or other of the shared source tracking issues. |
Hi @kinelski, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
1 similar comment
Hi @kinelski, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support. |
Track 2 data plane libraries that make use of LROs:
KeyVault is being tracked by #22912.
The text was updated successfully, but these errors were encountered: