-
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
Linting and Completeness fixes S360 #11958
Conversation
Merging from Azure to nasingla fork
Merge with Master
Rebase fork
…into Azure-master
Rebase fork
Swagger Validation Report
|
Rule | Message |
---|---|
The operation 'SubscriptionOperation_Get' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. New: Microsoft.Subscription/preview/2018-03-01-preview/subscriptions.json#L50 |
|
OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'SubscriptionOperationModel'. Consider using the plural form of 'SubscriptionOperation' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. New: Microsoft.Subscription/preview/2018-03-01-preview/subscriptions.json#L52 |
|
Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: getPendingSubscriptionOperations New: Microsoft.Subscription/preview/2018-03-01-preview/subscriptions.json#L53 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/subscription/resource-manager/readme.md tag: specification/subscription/resource-manager/readme.md#tag-package-2020-09 |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
Swagger Generation Artifacts
|
NewApiVersionRequired reason: |
Hi @navysingla, 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. |
Could you take a look at the lint issue? It seems in readme.md, you put preview/2018-11-01-preview/subscriptions.json and /preview/2018-03-01-preview/subscriptions.json together, which cause the conflict Tag: package-2019-03-preview input-file:
|
But in the past we have generated SDK with these versions together |
* New Version for subscription RP * S360 fixes * Update readme.md * Update subscriptions.json * Update subscriptions.json * Update subscriptions.json
* New Version for subscription RP * S360 fixes * Update readme.md * Update subscriptions.json * Update subscriptions.json * Update subscriptions.json
Swagger validation team added some new validations which triggered S360 on our team for old versions. Fixing swaggers for older versions to remove S360