We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This request is to generate SDK only. Do not release SDK SDK will be released later by service owner.
Requested by @praveenkuttappan Release Plan: 426 Link: test-repo-billy/azure-rest-api-specs#2958 Spec Type: TypeSpec Language: Go
Contacts: prmarott
Comments: Test SDK generation for TypeSpec using new process. Generate only.
Checklist: This checklist is used to make sure that common guidelines for an sdk generation are followed and SDK is ready to be released.
Requester comments for breaking reason
For example: we think this is a necessary change.
Breaking API spec links
For example: https://azure-rest-api-spec/xxxx
Changelog for this release For example: 12.0.0 (2020-06-19) Features
The text was updated successfully, but these errors were encountered:
Azure/azure-sdk-for-python#35118
Sorry, something went wrong.
No branches or pull requests
SDK generate request for Materialized Views
This request is to generate SDK only. Do not release SDK
SDK will be released later by service owner.
Requested by @praveenkuttappan
Release Plan: 426
Link: test-repo-billy/azure-rest-api-specs#2958
Spec Type: TypeSpec
Language: Go
Contacts:
prmarott
Comments:
Test SDK generation for TypeSpec using new process. Generate only.
Checklist:
This checklist is used to make sure that common guidelines for an sdk generation are followed and SDK is ready to be released.
Requester comments for breaking reason
For example: we think this is a necessary change.
Breaking API spec links
For example: https://azure-rest-api-spec/xxxx
Changelog for this release
For example:
12.0.0 (2020-06-19)
Features
The text was updated successfully, but these errors were encountered: