-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Adding Managed HSM support #8962
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 Managed HSM support #8962
Conversation
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-cli-extensions
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-go
|
azure-sdk-for-java
|
azure-sdk-for-js
|
azure-sdk-for-net
|
|
Can one of the admins verify this patch? |
heaths
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you email the OpenAPI Hub link containing the semantic diff? It's incredibly difficult to see what changed otherwise. See my various emails for 7.1-preview for an example, or just go to OpenAPI Hub and configure it. You may have to do it manually, ie. specify the branch URL and version for each.
| - Microsoft.KeyVault/preview/2018-02-14-preview/providers.json | ||
| ``` | ||
|
|
||
| ### Tag: package-preview-2020-04 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use the format as you see above. OpenAPI Hub may create this format, but it's inconsistent with all over services I looked at.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, Please find Open API Hub link below;
#8996
| @@ -0,0 +1,1835 @@ | |||
| { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's difficult to tell what was added or otherwise changed in GitHub this way. Please generate a semantic diff using the following instructions:
- Go to https://aka.ms/openapihub
- Click on Specs Diff & Change Log.
- Select Using OpenAPI Configuration File & Tag.
- Set the Source URL to the new or changed readme.md file, e.g. https://github.com/Azure/azure-rest-api-specs/blob/4ccfff0a78bee40837834c3780c2b10d8641bc62/specification/keyvault/resource-manager/readme.md
- Select the new version in Tags from Source URL, e.g. "package-preview-2020-04".
- Set the Target URL to the old readme.md file, e.g. https://github.com/Azure/azure-rest-api-specs/blob/master/specification/keyvault/resource-manager/readme.md
- Select the old version in Tags from Target URL, e.g. "package-2019-09".
- Click Compare!.
You can paste the link here. Note: I might have source and target reversed because the labels are not obvious. I've asked the OpenAPI Hub team to change this to just "old" and "new", for example.
KrisBash
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signing off with comment
| } | ||
| ], | ||
| "responses": { | ||
| "202": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the service behavior? While supported, 201/azure-asyncoperation is preferred/more common
|
Please fix CI following the doc. |
|
@riteshchitlangia1 please take a look at the comments. |
|
@riteshchitlangia1 is this PR still needed? |
No, this is not needed. |
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.