Key Vault keys API: Add OKP key type and EdDSA digital signature#15943
Key Vault keys API: Add OKP key type and EdDSA digital signature#15943docschmidt wants to merge 2 commits intoAzure:mainfrom
Conversation
|
Hi, @docschmidt 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 |
|---|---|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L476 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L518 |
|
| Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.KeyVault/preview/7.3-preview/rbac.json#L530 |
|
| The operation 'CreateCertificate' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Microsoft.KeyVault/preview/7.3-preview/certificates.json#L458 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️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.
️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
|
@docschmidt please answer the following from the checklist:
|
@tjprescott, the feature is already live in public regions. In regards to publishing the Swagger, I'll get back to you. |
| "OKP", | ||
| "OKP-HSM" |
There was a problem hiding this comment.
This is news to the Azure SDK team for 7.3-preview. Should this be in 7.4-preview?
/cc @jlichwa @maorleger
There was a problem hiding this comment.
If it is intended for 7.3-preview, is it supported in Key Vault and or Managed HSM? Do RPs in the public clouds already support it? If not, when? We need time to add support, write up tests, and record new sessions.
There was a problem hiding this comment.
Yes I was not aware of this either, and I agree that it is likely 7.4....
There was a problem hiding this comment.
Discussed this offline with Jack. I will cancel this PR, wait for 7.4-preview availability, and resubmit.
There was a problem hiding this comment.
Regarding 7.4-preview, what is the ETA for the branch/folder?
There was a problem hiding this comment.
It's already created but needs a PR to fully prep it. @jhendrixMSFT or @lmazuel can you merge PR #15900 ?
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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
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.