-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Added v2022-04-15-preview API for ArcAppliance #19491
Added v2022-04-15-preview API for ArcAppliance #19491
Conversation
Hi, @saisankargochhayat Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vscswagger@microsoft.com |
Swagger Validation Report
|
compared swaggers (via Oad v0.9.6)] | new version | base version |
---|---|---|
appliances.json | 2022-04-15(c3b630b) | 2021-10-31(main) |
The following breaking changes are detected by comparison with the latest preview version:
Rule | Message |
---|---|
The read only property has changed from 'true' to 'false'. New: Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L964:9 Old: Microsoft.ResourceConnector/preview/2021-10-31-preview/appliances.json#L686:9 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 2 Warnings warning [Detail]
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-2022-04-15-preview | package-2022-04-15-preview(c3b630b) | default(main) |
The following errors/warnings are introduced by current PR:
Rule | Message |
---|---|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L678 |
|
The child tracked resource, 'upgradeGraphs' with immediate parent 'appliance', must have a list by immediate parent operation. Location: Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L664 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json#L825 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️⚠️
SDK Track2 Validation: 4 Warnings warning [Detail]
- The following tags are being changed in this PR
Rule | Message |
---|---|
"readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > SupportedVersion > properties > metadata)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
"readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > SupportedVersionCatalogVersion > properties > data)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
"readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > SupportedVersionMetadata > properties > catalogVersion)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
"readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"Semantic violation: Sibling values alongside $ref will be ignored. See https://github.com/Azure/autorest/blob/main/docs/openapi/howto/$ref-siblings.md for allowed values (components > schemas > UpgradeGraph > properties > properties)\n keys: [ \u001b[32m'type'\u001b[39m ]" |
|
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"AutoRest core version selected from configuration: ^3.2.0." |
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.11.0 -> 1.11.0)" |
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.11.0->1.11.0)" |
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"> Installing AutoRest extension '@autorest/modelerfour' (4.21.4 -> 4.21.4)" |
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"> Installed AutoRest extension '@autorest/modelerfour' (4.21.4->4.21.4)" |
💬 | "readme":"resourceconnector/resource-manager/readme.md", "tag":"package-2022-04-15-preview", "details":"Autorest completed in 9.3s. 0 files generated." |
️️✔️
PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Hi @saisankargochhayat, Your PR has some issues. Please fix the CI sequentially by following the order of
|
/azp run |
Comment was made before the most recent commit for PR 19491 in repo Azure/azure-rest-api-specs |
Hi, @saisankargochhayat your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
...ctor/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json
Show resolved
Hide resolved
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove |
f7e4f17
to
2ae215c
Compare
...ctor/resource-manager/Microsoft.ResourceConnector/preview/2022-04-15-preview/appliances.json
Outdated
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy 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.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. 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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
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.
Please follow the link to find more details on PR review process.