-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Fix swagger file with missed API and properties #19605
Conversation
Hi, @Yiyao-MS 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 |
---|---|---|
ServiceOperations.json | 2021-12-01(9dc4c76) | 2021-12-01(main) |
mysql.json | 2021-05-01(9dc4c76) | 2021-05-01(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️
LintDiff: 4 Warnings warning [Detail]
compared tags (via openapi-validator v1.13.0) | new version | base version |
---|---|---|
package-flexibleserver-2021-05-01 | package-flexibleserver-2021-05-01(9dc4c76) | package-flexibleserver-2021-05-01(main) |
package-flexibleserver-2021-12-01-preview | package-flexibleserver-2021-12-01-preview(9dc4c76) | package-flexibleserver-2021-12-01-preview(main) |
The following errors/warnings are introduced by current PR:
Rule | Message |
---|---|
OperationId should contain the verb: 'checknameavailability' in:'CheckNameAvailabilityWithoutLocation_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L180 |
|
OperationId should contain the verb: 'checknameavailability' in:'CheckNameAvailabilityWithoutLocation_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1395 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Check name availability Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L181 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Check name availability Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1396 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
R4037 - MissingTypeObject |
The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2701 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2308 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2358 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2406 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2460 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2468 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2503 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2517 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2687 |
Since operation 'ConfigurationsBatchUpdate' response has model definition 'array', it should be of the form 'list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1154 |
|
OperationId should contain the verb: 'checkvirtualnetworksubnetusage' in:'CheckVirtualNetworkSubnetUsage_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L84 |
|
OperationId should contain the verb: 'checknameavailability' in:'CheckNameAvailability_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L132 |
|
OperationId should contain the verb: 'getprivatednszonesuffix' in:'GetPrivateDnsZoneSuffix_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L225 |
|
OperationId should contain the verb: 'updateconfigurations' in:'Configurations_BatchUpdate'. Consider updating the operationId Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1154 |
|
OperationId should contain the verb: 'checkvirtualnetworksubnetusage' in:'CheckVirtualNetworkSubnetUsage_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1299 |
|
OperationId should contain the verb: 'checknameavailability' in:'CheckNameAvailability_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1347 |
|
OperationId should contain the verb: 'getprivatednszonesuffix' in:'GetPrivateDnsZoneSuffix_Execute'. Consider updating the operationId Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L1440 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: nameAvailable Location: Microsoft.DBforMySQL/preview/2021-12-01-preview/ServiceOperations.json#L546 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: nameAvailable Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2567 |
|
The value provided for description is not descriptive enough. Accurate and descriptive description is essential for maintaining reference documentation. Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L2607 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Restart a server Location: Microsoft.DBforMySQL/stable/2021-05-01/mysql.json#L383 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/mysql/resource-manager/readme.md tag: specification/mysql/resource-manager/readme.md#tag-package-2020-01-01 |
️️✔️
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: 0 Warnings warning [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/9dc4c76286da9c102428e6257b86854ce30c3cf8/specification/mysql/resource-manager/readme.md#tag-package-flexibleserver-2021-05-01">mysql/resource-manager/readme.md#package-flexibleserver-2021-05-01
- "https://github.com/Azure/azure-rest-api-specs/blob/9dc4c76286da9c102428e6257b86854ce30c3cf8/specification/mysql/resource-manager/readme.md#tag-package-flexibleserver-2021-12-01-preview">mysql/resource-manager/readme.md#package-flexibleserver-2021-12-01-preview
Rule | Message |
---|---|
"readme":"mysql/resource-manager/readme.md", "tag":"package-flexibleserver-2021-05-01", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
|
"readme":"mysql/resource-manager/readme.md", "tag":"package-flexibleserver-2021-12-01-preview", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️
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
|
NewApiVersionRequired reason: |
Hi @Yiyao-MS, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @Yiyao-MS, 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. |
@Yiyao-MS Can you add this to the most recent preview version? That version is where we generate python SDK and use in CLI. We need backward compatibility in APIs |
Adding the approve-breaking-change label since the corresponding item has been approved: https://msazure.visualstudio.com/One/_workitems/edit/14960361 |
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.