Add xms-ids for notificationhubs #17909
Merged
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
|
Hi, @LinglingTong 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 |
|
[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 |
|---|---|
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L316 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L547 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/listKeys' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L594 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L645 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/notificationHubs/{notificationHubName}/AuthorizationRules/{authorizationRuleName}' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1037 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/notificationHubs/{notificationHubName}/AuthorizationRules' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1263 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/notificationHubs/{notificationHubName}/AuthorizationRules/{authorizationRuleName}/listKeys' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1317 |
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.NotificationHubs/namespaces/{namespaceName}/notificationHubs/{notificationHubName}/AuthorizationRules/{authorizationRuleName}/regenerateKeys' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1375 |
|
the default error response schema does not correspond to the schema documented at https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/common-api-details.md#error-response-content. Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L61 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L102 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L158 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L215 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L260 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L306 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L366 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L415 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L464 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L501 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L534 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L581 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L635 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L695 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L748 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L808 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L872 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L921 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L967 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1027 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1094 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.NotificationHubs/stable/2017-04-01/notificationhubs.json#L1150 |
️️✔️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 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).
Swagger Generation Artifacts
|
|
@mpodwysocki I see you contributed to this file earlier. Would you be able to help with a code review? Thanks! |
This was referenced Feb 18, 2022
Sure, I can do that |
Thanks so much! |
ArcturusZhang
approved these changes
Feb 24, 2022
|
Please let me know when this is ready to merge |
|
Hey @mpodwysocki just checking - is there any question I can help with answering regarding to the code review? |
@ArcturusZhang this PR is ready to merge. Thanks! |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Mar 2, 2022
Closed
[ReleasePR azure-resourcemanager-notificationhubs] update readme 7_10
Azure/azure-sdk-for-java#22586
Closed
FredericHeem
pushed a commit
to grucloud/azure-rest-api-specs
that referenced
this pull request
Mar 7, 2022
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:
About this Change
APIs will need to start indicating item uniqueness in arrays. By default, uniqueness is the string property called "id" of items in an array. When that property does not exist, the x-ms-identifiers extension property must be used to specify the identifying property(s) or lack thereof. This pull request is my best guess effort to ease resource providers into the new requirement before it becomes enforced. Compliance and accuracy will need to be owned and maintained by the resource provider going forward.
See https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-identifiers.
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.