azure-rest-api-specs
azure-rest-api-specs copied to clipboard
Published
20 hours ago •
Azure
Azure
Adding Container App Jobs specs for review | Draft
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow. Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
- What's the purpose of the update?
- [ ] new service onboarding
- [ ] new API version
- [ ] update existing version for new feature
- [ ] update existing version to fix swagger quality issue in s360
- [ ] Other, please clarify
- When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
- When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
- By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.
Contribution checklist (MS Employees Only):
- [ ] I commit to follow the Breaking Change Policy of "no breaking changes"
- [ ] I have reviewed the documentation for the workflow.
- [ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.
- Change to data plane APIs
- Adding new properties
- All removals
Otherwise your PR may be subject to ARM review requirements. Complete the following:
-
[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
- Adding a new service
- Adding new API(s)
- Adding a new API version -[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
-
[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
-
[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.
Hi, @anandanthony Thanks for your PR. I am workflow bot for review process. Here are some small tips.
![openapi-workflow-bot[bot] avatar](https://avatars.githubusercontent.com/in/81125?v=4 "Published by a pub.dev verified publisher"){kind=small}
Swagger Validation Report
️🔄BreakingChange inProgress [Detail]
️❌Breaking Change(Cross-Version): 41 Errors, 38 Warnings failed [Detail]
| compared swaggers (via Oad v0.10.2)] | new version | base version |
|---|---|---|
| CommonDefinitions.json | 2022-11-01-preview(989b96c) | 2022-10-01(main) |
| CommonDefinitions.json | 2022-11-01-preview(989b96c) | 2022-06-01-preview(main) |
| analyzeconversations-authoring.json | 2023-05-01(989b96c) | 2022-05-01(main) |
| analyzeconversations-authoring.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| analyzeconversations.json | 2023-05-01(989b96c) | 2022-05-01(main) |
| analyzeconversations.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| analyzetext-authoring.json | 2023-05-01(989b96c) | 2022-05-01(main) |
| analyzetext-authoring.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| analyzetext.json | 2023-05-01(989b96c) | 2022-05-01(main) |
| analyzetext.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| common.json | 2023-05-01(989b96c) | 2022-05-01(main) |
| common.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| questionanswering-authoring.json | 2023-05-01(989b96c) | 2021-10-01(main) |
| questionanswering-authoring.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
| questionanswering.json | 2023-05-01(989b96c) | 2021-10-01(main) |
| questionanswering.json | 2023-05-01(989b96c) | 2022-10-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
Only 17 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L30:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L79:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/deletion-jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L210:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/:export' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L249:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/export/jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L303:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/:import' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L345:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/import/jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L401:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments/{deploymentName}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L443:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments/{deploymentName}/jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L488:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L533:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/synonyms' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L585:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/sources' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L680:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/sources/jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L781:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/qnas' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L823:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/qnas/jobs/{jobId}' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L927:5 |
|
The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/feedback' removed or restructured? Old: Language/stable/2021-10-01/questionanswering-authoring.json#L969:5 |
|
The new version is missing a client parameter that was found in the old version. Was 'ConversationalAnalysisAuthoringFormatQueryParameter' removed or renamed? New: cognitiveservices/data-plane/Language/analyzeconversations-authoring.json#L3831:3 Old: Language/stable/2022-05-01/analyzeconversations-authoring.json#L3012:3 |
The following breaking changes are detected by comparison with the latest preview version:
| Rule | Message |
|---|---|
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L45:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L94:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/deletion-jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L225:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/:export' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L264:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/export/jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L318:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/:import' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L360:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/import/jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L416:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments/{deploymentName}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L458:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments/{deploymentName}/jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L503:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/deployments' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L548:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/synonyms' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L600:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/sources' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L695:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/sources/jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L796:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/qnas' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L838:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/qnas/jobs/{jobId}' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L942:5 |
| :warning: 1005 - RemovedPath | The new version is missing a path that was found in the old version. Was path '/query-knowledgebases/projects/{projectName}/feedback' removed or restructured? Old: Language/preview/2022-10-01-preview/questionanswering-authoring.json#L984:5 |
️🔄LintDiff inProgress [Detail]
️❌Avocado: 168 Errors, 34 Warnings failed [Detail]
Only 17 items are listed, please refer to log for more details.
️❌~[Staging] SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️🔄ModelValidation inProgress [Detail]
️❌SemanticValidation: 29 Errors, 0 Warnings failed [Detail]
Only 17 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/app/resource-manager/Microsoft.App/preview/2022-11-01-preview/examples/ContainerAppsJob_CreateOrUpdate.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/app/resource-manager/Microsoft.App/preview/2022-11-01-preview/examples/ContainerAppsJob_CreateOrUpdate.json' JsonUrl: Microsoft.App/preview/2022-11-01-preview/ContainerAppsJobs.json |
|
Missing required property: swagger JsonUrl: stable/2022-05-01/restler/annotations.json |
|
Missing required property: info JsonUrl: stable/2022-05-01/restler/annotations.json |
|
Missing required property: paths JsonUrl: stable/2022-05-01/restler/annotations.json |
|
Missing required property: swagger JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: openapi JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: servers JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: components JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: requestBody JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: schema JsonUrl: inference/stable/2022-12-01/inference.json |
|
Additional properties not allowed: content JsonUrl: inference/stable/2022-12-01/inference.json |
|
Missing required property: type JsonUrl: inference/stable/2022-12-01/inference.json |
|
Expected type object but found type string JsonUrl: Creator/preview/2022-09-01-preview/wayfind.json#L236:13 |
|
Missing required property: swagger JsonUrl: inference/preview/2022-06-01-preview/inference.json |
|
Additional properties not allowed: openapi JsonUrl: inference/preview/2022-06-01-preview/inference.json |
|
Additional properties not allowed: servers JsonUrl: inference/preview/2022-06-01-preview/inference.json |
|
Additional properties not allowed: components JsonUrl: inference/preview/2022-06-01-preview/inference.json |
️❌PrettierCheck: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
Code style issues found path: Microsoft.App/preview/2022-11-01-preview/ContainerAppsJobs.json |
️❌SpellCheck: 70 Errors, 0 Warnings failed [Detail]
Only 17 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Unknown word (parellelism), please fix the error or add words to ./custom-words.txt path: Microsoft.App/preview/2022-11-01-preview/ContainerAppsJobs.json#L444:112 |
|
Unknown word (parellelism), please fix the error or add words to ./custom-words.txt path: Microsoft.App/preview/2022-11-01-preview/ContainerAppsJobs.json#L455:126 |
|
Unknown word (Remediatable), please fix the error or add words to ./custom-words.txt path: Microsoft.Authorization/preview/2022-08-01-preview/RoleManagementAlerts.json#L1080:12 |
|
Unknown word (vhdx), please fix the error or add words to ./custom-words.txt path: Microsoft.AzureStackHCI/preview/2021-09-01-preview/virtualHardDisks.json#L332:67 |
|
Unknown word (vhdx), please fix the error or add words to ./custom-words.txt path: Microsoft.AzureStackHCI/preview/2021-09-01-preview/virtualHardDisks.json#L334:14 |
|
Unknown word (Noreuse), please fix the error or add words to ./custom-words.txt path: Microsoft.ContainerInstance/preview/2022-10-01-preview/containerInstance.json#L1735:14 |
|
Unknown word (Noreuse), please fix the error or add words to ./custom-words.txt path: Microsoft.ContainerInstance/stable/2022-09-01/containerInstance.json#L1710:14 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/LinkedService.json#L5826:6 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/LinkedService.json#L5827:36 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/LinkedService.json#L5828:23 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/LinkedService.json#L5837:27 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/Pipeline.json#L3580:6 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/Pipeline.json#L3581:39 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/Pipeline.json#L3594:73 |
|
Unknown word (Netezza), please fix the error or add words to ./custom-words.txt path: stable/2018-06-01/entityTypes/Pipeline.json#L3598:67 |
|
Unknown word (tmpfs), please fix the error or add words to ./custom-words.txt path: Microsoft.MachineLearningServices/preview/2022-10-01-preview/machineLearningServices.json#L5039:14 |
|
Unknown word (npipe), please fix the error or add words to ./custom-words.txt path: Microsoft.MachineLearningServices/preview/2022-10-01-preview/machineLearningServices.json#L5040:14 |
️❌CadlValidation: 2 Errors, 18 Warnings failed [Detail]
Only 17 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
"details":"The generated swagger file 2022-06-27-preview/Qumulo.Storage.json from cadl specification/liftrqumulo/Qumulo.Management is not the same as the '/mnt/vss/_work/1/azure-rest-api-specs/specification/liftrqumulo/resource-manager/Qumulo.Storage/preview/2022-06-27-preview/Qumulo.Storage.json' in PR, please make sure the swagger is consistent with the generated swagger. You can find the difference in the pipeline log." |
|
"details":"The generated swagger file 2022-10-12-preview/Qumulo.Storage.json from cadl specification/liftrqumulo/Qumulo.Management is not the same as the '/mnt/vss/_work/1/azure-rest-api-specs/specification/liftrqumulo/resource-manager/Qumulo.Storage/preview/2022-10-12-preview/Qumulo.Storage.json' in PR, please make sure the swagger is consistent with the generated swagger. You can find the difference in the pipeline log." |
| :warning: @azure-tools/cadl-azure-core/use-extensible-enum | Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/univariate/models.cadl#L33 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'DetectUnivariateEntireSeries' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/univariate/routes.cadl#L10 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'DetectUnivariateChangePoint' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/univariate/routes.cadl#L38 |
| :warning: @azure-tools/cadl-azure-core/casing-style | The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/models.cadl#L97 |
| :warning: @azure-tools/cadl-azure-core/use-extensible-enum | Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/multivariate/models.cadl#L35 |
| :warning: @azure-tools/cadl-azure-core/use-extensible-enum | Enums should be defined without the @fixed decorator.Location: cognitiveservices/AnomalyDetector/multivariate/models.cadl#L41 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'TrainMultivariateModel' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L25 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'ListMultivariateModels' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L48 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'GetMultivariateModel' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L79 |
| :warning: @azure-tools/cadl-azure-core/casing-style | The names of Property types must use camelCase Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L112 |
| :warning: @azure-tools/cadl-azure-core/use-standard-operations | Operation 'DetectMultivariateLastAnomaly' should be defined using a signature from the Azure.Core namespace. Location: cognitiveservices/AnomalyDetector/multivariate/routes.cadl#L119 |
| :warning: @azure-tools/cadl-providerhub/non-breaking-versioning | Adding required property is a breaking change. Location: specification/liftrqumulo/Qumulo.Management/main.cadl#L76 |
| :warning: @azure-tools/cadl-providerhub/non-breaking-versioning | Adding required property is a breaking change. Location: specification/liftrqumulo/Qumulo.Management/main.cadl#L85 |
| :warning: @azure-tools/cadl-azure-resource-manager/missing-operations-endpoint | Arm namespace Storage is missing the Operations interface. Add "interface Operations extends Azure.ResourceManager.Operations {}". Location: specification/liftrqumulo/Qumulo.Management/main.cadl#L12 |
| :warning: @azure-tools/cadl-azure-resource-manager/resource-name | The resource 'name' field should be marked with 'read' visibility and an @path decorator. Location: specification/liftrqumulo/Qumulo.Management/main.cadl#L36 |
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
![openapi-pipeline-app[bot] avatar](https://avatars.githubusercontent.com/in/65541?v=4 "Published by a pub.dev verified publisher"){kind=small}
Swagger Generation Artifacts
️️✔️ApiDocPreview succeeded [Detail] [Expand]
Only 0 items are rendered, please refer to log for more details.
️⚠️SDK Breaking Change Tracking warning [Detail]
Only 0 items are rendered, please refer to log for more details.
️❌ azure-sdk-for-net-track2 failed [Detail]
Only 0 items are rendered, please refer to log for more details.
️⚠️ azure-sdk-for-python warning [Detail]
Only 0 items are rendered, please refer to log for more details.
️❌ azure-sdk-for-java failed [Detail]
Only 0 items are rendered, please refer to log for more details.
️❌ azure-sdk-for-go failed [Detail]
Only 0 items are rendered, please refer to log for more details.
️🔄 azure-resource-manager-schemas inProgress [Detail]
️🔄 azure-powershell inProgress [Detail]
️❌ azure-sdk-for-python-track2 failed [Detail]
Only 0 items are rendered, please refer to log for more details.
️🔄 azure-sdk-for-js inProgress [Detail]
️❌ azure-sdk-for-net failed [Detail]
Only 0 items are rendered, please refer to log for more details.
Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.
Hi, @anandanthony, For review efficiency consideration, when creating a new api version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki. Or you could onboard API spec pipeline
Hi @anandanthony, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. Action: To initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki. If you want to know the production traffic statistic, please see ARM Traffic statistic. If you think it is false positive breaking change, please provide the reasons in the PR comment, report to Swagger Tooling Team via https://aka.ms/swaggerfeedback. Note: To avoid breaking change, you can refer to Shift Left Solution for detecting breaking change in early phase at your service code repository.
Hi @anandanthony, one or multiple validation error/warning suppression(s) is detected in your PR. Please follow the Swagger-Suppression-Process to get approval.