-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Compare python SDK for compute TypeSpec migration #38620
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @amjads1 @Drewm3 @GabstaMSFT @sandeepraichura @TravisCragg-MSFT. |
Breakings that may be caused by Typespec migration:
|
Python SDK domain breakings:
|
Python SDK domain breakings but not influence SDK users:
|
Hi @msyyc,the issue of the removal of |
We are working on the compute TypeSpec migration.
Would like python to verify the SDK generation of the corresponding swagger of the converted TypeSpec.
We have split compute into multiple sub services and done the conversion for each of them.
For instance, Compute sub-service:
The text was updated successfully, but these errors were encountered: