-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Added swagger for private link resource API #8655
Conversation
Can one of the admins verify this patch? |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-js - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-java - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-python - Release
|
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Outdated
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Outdated
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Outdated
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Outdated
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
azure-cli-extensions - Release
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
|
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Show resolved
Hide resolved
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Show resolved
Hide resolved
PeRrpSwagger
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
...n/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2016-06-01/vaults.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
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 @deymadhumanti please resolve the CI failures (Spell check and prettier). And as for the breaking changes check, could you provide a justification of this? Or it is only a false alarm? Hi @ChenTanyi would you please take a look at the Java generation failure? |
The generation error is due to |
@ChenTanyi No idea, you know as much as I know about v2 generator. My suggestion is to try another name for "PrivateLinkResources" definition, like "PrivateLinkResourceListResult". E.g. https://github.com/Azure/azure-rest-api-specs/blob/master/specification/cosmos-db/resource-manager/Microsoft.DocumentDB/preview/2019-08-01-preview/privateLinkResources.json#L117 |
@deymadhumanti Could you change for this name, if you want to update Java sdk. Thanks! |
Hi @ChenTanyi , Can we use "PrivateLinkResourceList" for PrivateLinkResources. Please confirm. I will make the json change accordingly, |
@deymadhumanti Yes, it could be It could be anything you like which could be separated from other resources and their plurality. |
Hi @ArcturusZhang , Prettier Check is successful here. I am looking at SpellCheck failure and update it . |
Hi @ArcturusZhang , Regarding breaking change failure: The earlier schema for CheckNameAvailability response was erronous. It was added as part of Added Swagger details for CheckNameAvailability API #5496 and OAV example validation wasn’t performed as a part of validation for the same. SDK has not been generated for the same since the swagger changes were made. With the current PR we are fixing the response to CheckNameAvailability API and we have also validated the same using OAV spec and example validation tool. It is in accordance with format mentioned at - https://github.com/Azure/azure-resource-manager-rpc/blob/master/v1.0/proxy-api-reference.md#check-name-availability-requests |
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @ChenTanyi , I have changed PrivateLinkResources to PrivateLinkResourceList. But still Java SDK generation is failing with same error. Can you please take a look |
I think the breaking changes are reasonable based on what you said. But since the breaking changes CI is a required check, this PR must wait for @akning-ms 's approval and eventually merge. |
@deymadhumanti After my test, it is not the error caused by items, the The problem is in operations, java always use operations in plural format. |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @akning-ms, Can you please take a look at this PR. |
* Added GEt-privateLinkResources API and managedIdentity changes for Vaults * Fixed PrettierCheck failure * Update vaults.json * Update vaults.json * Resolved PR commens related to PrivateLinkResources * Resolved PR comments * resolved PR comments * Using x-ms-client-flatten for PrivateLinkResourceProperties * Fixing examples for PrivateLinkResources * Revert "Fixing examples for PrivateLinkResources" This reverts commit b0d62a2. * Revert "Using x-ms-client-flatten for PrivateLinkResourceProperties" This reverts commit 31ba2d0. * Using x-ms-client-flatten for PrivateLinkResourceProperties * Fixing examples for PrivateLinkResources * Adding description for privateLinkResourceProperties * Resolved PR comments. Fixed SpellCheck and PrettierCheck and Java SDK failures * Changing operationId for PrivateLinkResource to PrivateLinkResources * Renaming PrivateLinkResourceList to PrivateLinkResources Co-authored-by: deymadhumanti <deymadhumanti@users.noreply.github.com> Co-authored-by: asmaskar <asmaskar@microsoft.com> Co-authored-by: asmaskar <58723769+asmaskar@users.noreply.github.com> Co-authored-by: Aman Chandna <amchandn@microsoft.com>
…ults
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.