-
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
Adding xms-ids for Attestation #17591
Adding xms-ids for Attestation #17591
Conversation
Hi, @agalerrotaru 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. |
Swagger Validation Report
|
Rule | Message |
---|---|
R4009 - RequiredReadOnlySystemData |
The response of operation:'PrivateEndpointConnections_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L316 |
R4009 - RequiredReadOnlySystemData |
The response of operation:'PrivateEndpointConnections_Create' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L359 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.Attestation/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L30 |
R4036 - ImplementPrivateEndpointAPIs |
The private endpoint API: /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Attestation/attestationProviders/{providerName}/privateLinkResources is missing. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L29 |
R4037 - MissingTypeObject |
The schema 'OperationList' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L612 |
R4037 - MissingTypeObject |
The schema 'AttestationProvider' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L668 |
R4037 - MissingTypeObject |
The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L724 |
R4037 - MissingTypeObject |
The schema 'CloudErrorBody' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L733 |
R4037 - MissingTypeObject |
The schema 'AttestationProviderListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L747 |
R4037 - MissingTypeObject |
The schema 'AttestationServicePatchParams' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L764 |
R4037 - MissingTypeObject |
The schema 'AttestationServiceCreationParams' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L777 |
R4037 - MissingTypeObject |
The schema 'AttestationServiceCreationSpecificParams' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L802 |
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L796 |
|
The operation 'AttestationProviders_Delete' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L222 |
|
A PUT operation request body schema should be the same as its 200 response schema, to allow reusing the same entity between GET and PUT. If the schema of the PUT request body is a superset of the GET response body, make sure you have a PATCH operation to make the resource updatable. Operation: 'AttestationProviders_Create' Request Model: 'AttestationServiceCreationParams' Response Model: 'AttestationProvider' Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L108 |
|
Based on the response model schema, operation 'Operations_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L31 |
|
Based on the response model schema, operation 'AttestationProviders_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L456 |
|
Based on the response model schema, operation 'AttestationProviders_ListByResourceGroup' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L492 |
|
Based on the response model schema, operation 'AttestationProviders_ListDefault' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.Attestation/stable/2020-10-01/attestation.json#L531 |
|
The child tracked resource, 'privateEndpointConnections' with immediate parent 'AttestationProvider', must have a list by immediate parent operation. Location: common-types/resource-management/v1/privatelinks.json#L20 |
|
'JSONWebKey' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: specification/common-types/rfcs/rfc7517.json#L9 |
|
'JSONWebKeySet' model/property lacks 'description' and 'title' property. Consider adding a 'description'/'title' element. Accurate description/title is essential for maintaining reference documentation. Location: specification/common-types/rfcs/rfc7517.json#L88 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
~[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 succeeded [Detail] [Expand]
There are no breaking changes.
️❌
CredScan: 0 Errors, 0 Warnings failed [Detail]
️️✔️
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).
Thank you for your contribution agalerrotaru! We will review the pull request and get back to you soon. |
Swagger Generation Artifacts
|
@colawwj I see an SDK breaking change tracking error that is not related to my changes - I believe this should be legacy issues from earlier PRs. Please advise, so I can get unblocked. Thanks! |
* Adding xms-ids for Attestation * revert common types file
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.