DiskRP swagger 2021-12-01 #17709
Merged
DiskRP swagger 2021-12-01 #17709
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rytruong
requested review from
dkulkarni-ms,
grizzlytheodore,
haagha,
hyonholee,
madewithsmiles,
MS-syh2qs and
Sandido
as code owners
|
Hi, @rytruong 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 |
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L67 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L165 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L227 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L261 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L298 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L331 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L379 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L425 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L474 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L533 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L577 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L611 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L648 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L681 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L729 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L772 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1430 |
|
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1858 |
|
The schema 'ProxyOnlyResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1893 |
|
The schema 'Disk' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1913 |
|
The schema 'DiskUpdate' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1954 |
|
The schema 'DiskList' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1973 |
|
The schema 'DiskSku' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L1992 |
|
The schema 'SnapshotSku' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2044 |
|
The schema 'DiskProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2081 |
|
The schema 'SnapshotProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2238 |
|
The schema 'ShareInfoElement' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2350 |
|
The schema 'EncryptionSetProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2359 |
|
The schema 'EncryptionSettingsCollection' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2401 |
|
The schema 'EncryptionSettingsElement' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Compute/stable/2021-12-01/disk.json#L2427 |
️⚠️Avocado: 1 Warnings warning [Detail]
| Rule | Message |
|---|---|
| The default tag contains multiple API versions swaggers. readme: specification/compute/resource-manager/readme.md tag: specification/compute/resource-manager/readme.md#tag-package-2021-12-01 |
️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️Cross-Version Breaking Changes: 18 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.3)
- current:stable/2021-12-01/disk.json compared with base:stable/2021-08-01/disk.json
- current:stable/2021-12-01/disk.json compared with base:preview/2016-04-30-preview/disk.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️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).
|
[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. |
ghost
added
the
Swagger Generation Artifacts
|
|
Hi, @rytruong your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
|
Hi @rytruong, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Feb 8, 2022
chetmaddula
reviewed
Feb 8, 2022
specification/compute/resource-manager/Microsoft.Compute/stable/2021-08-01/disk.json
Outdated
Show resolved
Hide resolved
chetmaddula
reviewed
Feb 8, 2022
specification/compute/resource-manager/Microsoft.Compute/stable/2021-12-01/disk.json
Outdated
Show resolved
Hide resolved
ArcturusZhang
added
the
DoNotMerge
grizzlytheodore
removed
the
DoNotMerge
|
@ArcturusZhang this is ready for merge. The internal communications for Arm64 architecture is resolved and have been added to this PR |
chetmaddula
approved these changes
Feb 23, 2022
|
last commit is syncing with change that went into 2021-08-01 version few days ago #17633 |
|
Well. the x-ms-identifiers is causing some issues for the track 1 generation. I am fixing it in this PR and merge that first. |
ArcturusZhang
approved these changes
Feb 25, 2022
This was referenced Feb 25, 2022
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
Mar 7, 2022
* inital commit for diskrp swagger 2021-12-01 * added architecture * updated api version for example files * added dataAccessAuthMode * added architecture and dataAccessAuthMode * updated description for DataAccessAuthMode * Addressed comments * added xms-ids * Update readme.md Co-authored-by: REDMOND\rytruong <rytruong@microsoft.com> Co-authored-by: Theodore Chang <thchan@microsoft.com> Co-authored-by: ArcturusZhang <dapzhang@microsoft.com>
25 tasks
Sandido
pushed a commit
that referenced
this pull request
Mar 14, 2022
* inital commit for diskrp swagger 2021-12-01 * added architecture * updated api version for example files * added dataAccessAuthMode * added architecture and dataAccessAuthMode * updated description for DataAccessAuthMode * Addressed comments * added xms-ids * Update readme.md Co-authored-by: REDMOND\rytruong <rytruong@microsoft.com> Co-authored-by: Theodore Chang <thchan@microsoft.com> Co-authored-by: ArcturusZhang <dapzhang@microsoft.com>
25 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 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 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.