-
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
StoragePool GA Swagger Release #15760
Conversation
Hi, @harshitha-akkaraju 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. vsswagger@microsoft.com |
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Hi, @harshitha-akkaraju your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
Swagger Validation Report
|
Swagger Generation Artifacts
|
Hi @harshitha-akkaraju, Your PR has some issues. Please fix the CI sequentially by following the order of
|
...cation/storagepool/resource-manager/Microsoft.StoragePool/stable/2021-08-01/storagepool.json
Show resolved
Hide resolved
...pool/resource-manager/Microsoft.StoragePool/stable/2021-08-01/examples/IscsiTargets_Put.json
Show resolved
Hide resolved
...pool/resource-manager/Microsoft.StoragePool/stable/2021-08-01/examples/IscsiTargets_Get.json
Show resolved
Hide resolved
...pool/resource-manager/Microsoft.StoragePool/stable/2021-08-01/examples/IscsiTargets_Get.json
Show resolved
Hide resolved
Swagger Validation Report
|
Rule | Message |
---|---|
R3006 - BodyTopLevelProperties |
Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity, zones. Model definition 'DiskPool' has extra properties ['managedByExtended']. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1410 |
R3006 - BodyTopLevelProperties |
Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity, zones. Model definition 'IscsiTarget' has extra properties ['managedByExtended']. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1694 |
R3006 - BodyTopLevelProperties |
Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity, zones. Model definition 'IscsiTargetCreate' has extra properties ['managedByExtended']. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1727 |
R3006 - BodyTopLevelProperties |
Top level properties should be one of name, type, id, location, properties, tags, plan, sku, etag, managedBy, identity, zones. Model definition 'IscsiTargetUpdate' has extra properties ['managedByExtended']. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1754 |
The following errors/warnings exist before current PR submission:
Rule | Message |
---|---|
R4037 - MissingTypeObject |
The schema 'DiskPoolZoneListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1358 |
R4037 - MissingTypeObject |
The schema 'TrackedResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L2083 |
R4037 - MissingTypeObject |
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L2116 |
R4037 - MissingTypeObject |
The schema 'ErrorAdditionalInfo' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L2145 |
R4037 - MissingTypeObject |
The schema 'ErrorResponse' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L2160 |
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isDataAction Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1021 |
|
Booleans are not descriptive and make them hard to use. Consider using string enums with allowed set of values defined. Property: isAccessible Location: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1133 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌
Cross-Version Breaking Changes: 4 Errors, 0 Warnings failed [Detail]
- Compared Swaggers (Based on Oad v0.9.0)
- current:stable/2021-08-01/storagepool.json compared with base:preview/2021-04-01-preview/storagepool.json
Rule | Message |
---|---|
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1380:9 Old: Microsoft.StoragePool/preview/2021-04-01-preview/storagepool.json#L1093:9 |
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1388:9 Old: Microsoft.StoragePool/preview/2021-04-01-preview/storagepool.json#L1100:9 |
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1360:9 Old: Microsoft.StoragePool/preview/2021-04-01-preview/storagepool.json#L1075:9 |
1029 - ReadonlyPropertyChanged |
The read only property has changed from 'false' to 'true'. New: Microsoft.StoragePool/stable/2021-08-01/storagepool.json#L1368:9 Old: Microsoft.StoragePool/preview/2021-04-01-preview/storagepool.json#L1082:9 |
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
|:speech_balloon: AutorestCore/Exception|"readme":"storagepool/resource-manager/readme.md",
"tag":"package-2021-08-01",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"storagepool/resource-manager/readme.md",
"tag":"package-2021-08-01",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"storagepool/resource-manager/readme.md",
"tag":"package-2021-08-01",
"details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)"|
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
These settings apply only when `--tag=package-2021-08-01 --go` is specified on the command line. | ||
Please also specify `--go-sdks-folder=<path to the root directory of your azure-sdk-for-go clone>`. | ||
|
||
```yaml $(tag) == 'package-2021-04-01-preview' && $(go) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @harshitha-akkaraju , should the tag be package-2021-08-01 here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@changlong-liu just pushed a revision. thanks for catching it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@changlong-liu the go sdk generation still seems to be failing -- do you have any pointers on how to fix it?
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @ArcturusZhang , would you help have a look at whether the go sdk failure comes from this PR? Thanks. |
Co-authored-by: Arcturus <dapzhang@microsoft.com>
Note that my approval is only for the changes in |
/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:
08/28/2021
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 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.
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.