-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Convert StorageActions Swagger to TypeSpec #34150
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
base: main
Are you sure you want to change the base?
Conversation
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
Next Steps to MergeNext steps that must be taken to merge this PR:
|
PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
specification/storageactions/StorageAction.Management/StorageTask.tsp
Outdated
Show resolved
Hide resolved
…into StorageAction-TypeSpec-complie
This reverts commit 8056611.
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run SDK Validation - JS |
Azure Pipelines successfully started running 1 pipeline(s). |
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
…cgallan/azure-rest-api-specs into StorageAction-TypeSpec-complie
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
This PR migrates your latest version (identified by the tag in your readme.md) of swagger to TypeSpec. We already tried our best to make sure the TypeSpec represents same as previous swagger. Since we lack the business knowledge, please validate this PR again to make sure it's functional equivalent as before. The local validation step is at Getting started | TypeSpec Azure
Besides, TypeSpec encourages to follow ARM guidelines. Therefore, some representations in your previous swagger will be fixed to follow these guidelines. When you see differences in your local validation, please keep this note in mind.
Please reach out to TypeSpec Discussions Channel if there is any help needed.