[Search] Fix cspell Issues #22948
[Search] Fix cspell Issues #22948
Conversation
kashifkhan
force-pushed
the
search_spelling
branch
from
e41e6ec
to
1bd64a5
Compare
|
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
…into new_metrics_advisor * 'main' of https://github.com/Azure/azure-sdk-for-python: (62 commits) pass polling interval 0 for playback (Azure#23514) [webpubsub] switch to customizations code (Azure#23504) [AutoRelease] t2-netapp-2022-02-11-58164(Do not merge) (Azure#23214) [Key Vault] Address architect feedback (Azure#23475) Sync eng/common directory with azure-sdk-tools for PR 2910 (Azure#23499) check content (Azure#23496) fix cspell issues (Azure#22948) API Key Not Being Passed On Paged Requests (Azure#23477) [AutoRelease] t2-labservices-2022-03-14-64385 (Azure#23492) [Release issue status] fix date bug and serve Python only (Azure#23491) [SchemaRegistry] migrate to test proxy (Azure#23438) [compute] update test (Azure#23456) update servicebus test (Azure#23401) Update search test (Azure#23341) Update resources test (Azure#23340) Update relay test (Azure#23339) Update notificationhubs test (Azure#23338) Update network-dns test (Azure#23337) update network test (Azure#23421) update logic (Azure#23463) ...
Azure SignalR - Adding new api-version 2023-03-01-preview (Azure#22948) * init 2023-03-01-preview for signalr and webpubsub. Copied from 2022-02-01 * add new api version 2023-03-01-preview * revert changes to package-lock.json and package.json * 1. Add restart to replica 2. replica tracedResource, subscriptionId, resourceGroup, apiVersion within commonTYpe in v5 3. return 202 for patch operation 4. add 'x-ms-long-running-operation-options' for put operation 5. Add pattern to resourceName and replicaName * 1. Change response status code to 202 for patch 2. Fix the example naming 3. Add location header for post 202, change 'final-state-via' property to 'location' for POST * 1. Fix example response body 2. Fix "x-ms-long-running-operation-options" for put * 1. Fix example response body 2. Fix LocationHeader for PATCH * 1. Remove SystemData form models inherited from "Resource" 2. Reuse trackedResource, privateEndpointConnection, privateEndpointConnectionName * Fix default value of clientCertEnabled * Revert privateEndpointConnection since model in common is different from ours * Fix the resourceName pattern and example * fix naming pattern * 1. Add 200 for signalrRegenerate Key 2. fmt example
Azure SignalR - Adding new api-version 2023-03-01-preview (Azure#22948) * init 2023-03-01-preview for signalr and webpubsub. Copied from 2022-02-01 * add new api version 2023-03-01-preview * revert changes to package-lock.json and package.json * 1. Add restart to replica 2. replica tracedResource, subscriptionId, resourceGroup, apiVersion within commonTYpe in v5 3. return 202 for patch operation 4. add 'x-ms-long-running-operation-options' for put operation 5. Add pattern to resourceName and replicaName * 1. Change response status code to 202 for patch 2. Fix the example naming 3. Add location header for post 202, change 'final-state-via' property to 'location' for POST * 1. Fix example response body 2. Fix "x-ms-long-running-operation-options" for put * 1. Fix example response body 2. Fix LocationHeader for PATCH * 1. Remove SystemData form models inherited from "Resource" 2. Reuse trackedResource, privateEndpointConnection, privateEndpointConnectionName * Fix default value of clientCertEnabled * Revert privateEndpointConnection since model in common is different from ours * Fix the resourceName pattern and example * fix naming pattern * 1. Add 200 for signalrRegenerate Key 2. fmt example
Resolves #22672