-
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
[Hub Generated] Review request for Microsoft.Automanage to add version preview/2021-04-30-preview and stable/2022-05-04 #19170
[Hub Generated] Review request for Microsoft.Automanage to add version preview/2021-04-30-preview and stable/2022-05-04 #19170
Conversation
…-04-30-preview to version 2022-05-04
…s://github.com/mc3784/azure-rest-api-specs into dev-automanage-Microsoft.Automanage-2022-05-04
Hi, @mc3784 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
|
Rule | Message |
---|---|
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L2294:9 Old: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L2294:9 |
️⚠️
LintDiff: 4 Warnings warning [Detail]
- Linted configuring files (Based on source branch, openapi-validator v1.13.0 , classic-openapi-validator v1.2.4 )
- Linted configuring files (Based on target branch, openapi-validator v1.13.0 , classic-openapi-validator v1.2.4 )
Rule | Message |
---|---|
The child tracked resource, 'versions' with immediate parent 'ConfigurationProfile', must have a list by immediate parent operation. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2117 |
|
The child tracked resource, 'reports' with immediate parent 'ConfigurationProfileAssignment', must have a list by immediate parent operation. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2276 |
|
The child tracked resource, 'reports' with immediate parent 'ConfigurationProfileAssignment', must have a list by immediate parent operation. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2276 |
|
The child tracked resource, 'reports' with immediate parent 'ConfigurationProfileAssignment', must have a list by immediate parent operation. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2276 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L221 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L287 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L388 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,versionName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L543 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,versionName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L616 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,versionName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L731 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L800 |
R4039 - ParametersOrder |
The parameters:configurationProfileAssignmentName,resourceGroupName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L855 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L924 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L977 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,reportName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L1219 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L1281 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L221 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L287 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L388 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,versionName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L543 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,versionName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L616 |
R4039 - ParametersOrder |
The parameters:configurationProfileName,resourceGroupName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L733 |
R4039 - ParametersOrder |
The parameters:configurationProfileAssignmentName,resourceGroupName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L788 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L857 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L910 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,reportName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L1152 |
R4039 - ParametersOrder |
The parameters:resourceGroupName,configurationProfileAssignmentName,vmName should be kept in the same order as they present in the path. Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L1214 |
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: authorizationSet Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L2497 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: authorizationSet Location: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2430 |
|
The API version:2021-04-30-preview having been in a preview state over one year , please move it to GA or retire. Location: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L4 |
️️✔️
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.
️⚠️
Cross-Version Breaking Changes: 2 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.5)
- current:stable/2022-05-04/automanage.json compared with base:preview/2021-04-30-preview/automanage.json
Rule | Message |
---|---|
The read only property has changed from 'false' to 'true'. New: Microsoft.Automanage/stable/2022-05-04/automanage.json#L2227:9 Old: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L2294:9 |
|
The new version is missing an operation that was found in the old version. Was operationId 'ConfigurationProfilesVersions_Update' removed or restructured? New: Microsoft.Automanage/stable/2022-05-04/automanage.json#L542:5 Old: Microsoft.Automanage/preview/2021-04-30-preview/automanage.json#L542:5 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
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).
Swagger Generation Artifacts
|
Hi @mc3784, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @mc3784, 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. |
Hi, @mc3784 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
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:
Contribution checklist (MS Employees Only):
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 apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] 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.