-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[KeyVault] - Add exclusion for known spellcheck issue #18031
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
[KeyVault] - Add exclusion for known spellcheck issue #18031
Conversation
|
Hi, @maorleger 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. [email protected] |
|
[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
|
Swagger Generation Artifacts
|
|
@heaths not sure why pipeline is pending for public.rest-api-specs - do you know who owns this pipeline or who I can reach out to? |
|
According to https://github.com/Azure/azure-rest-api-specs/pull/18031/checks?check_run_id=5366659603 it completed. Seems to be an AzDO/GitHub interaction issue. I've seen these too many times before. @lmazuel can you merge this so we can proceed with the Key Vault / Managed HSM swagger GA? |
c5fb4a5 to
abf03f1
Compare
|
@lmazuel friendly ping - would you mind merging this for us? The builds all pass, just seems that GH isn't getting updated... |
|
/azp run public.rest-api-specs |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@akning-ms the public.rest-api-specs pipeline, despite succeeding, is not reporting back status rather frequently. On this PR it's been twice. I restarted the pipeline and it again completed successfully. Can someone from your team look into this? As the only "error" preventing checks from passing, I cannot merge this and we have to have admins do it. @lmazuel can you please merge this? Despite what checks show here, if you go to the checks tab itself it shows all pipelines passed. Unfortunately, that's not enough to allow me to merge it. This will hold up our KV release. |
…stable/7.3 (#18028) * Adds base for updating Microsoft.KeyVault from version preview/7.3-preview to version 7.3 * Updates readme * Updates API version in new specs and examples * [KeyVault] - Add exclusion for known spellcheck issue (#18031) * add exclusion for known spellcheck issue * collapse cspell ignore for keyvault's storage.json
…stable/7.3 (Azure#18028) * Adds base for updating Microsoft.KeyVault from version preview/7.3-preview to version 7.3 * Updates readme * Updates API version in new specs and examples * [KeyVault] - Add exclusion for known spellcheck issue (Azure#18031) * add exclusion for known spellcheck issue * collapse cspell ignore for keyvault's storage.json
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.