-
Notifications
You must be signed in to change notification settings - Fork 5.6k
ASR : swagger changes for zone to zone recovery plan #7985
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
Conversation
|
You don't have permission to trigger SDK Automation. |
|
Can one of the admins verify this patch? |
|
Model validation and semantic validations are not due to this PR and are being fixed as a separate PR : #7863 |
|
@myronfanqiu please take a look at this PR. Also please note that the changes are not breaking changes. thanks |
|
@vigaur Could you solve the CI errors? You need to change the swagger spec and change the example files. |
|
@myronfanqiu Please note that the Model validation and semantic validation errors are not result of current changes, Another PR is being raised for it along with #7863 Also please let me know who should be added to get the ARM feedback for the PR, thanks |
...vicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2018-07-10/service.json
Show resolved
Hide resolved
|
@myronfanqiu I understand the concern, though since these examples involve multiple stakeholders, we are taking this as back log item and will raise a separate PR for this, thanks |
|
@vigaur Hello. We still need ARM's review. BTW, I don't have the right to merge it without CI pass. I will invite the correct person to help you. |
|
@NullMDR Could you involve the right person to help on this PR? @vigaur want to merge this PR without CI pass. |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@vigaur Please supress model validation error in readme.md. You can reference https://github.com/Azure/azure-rest-api-specs/blob/master/specification/network/resource-manager/readme.md#suppression as example |
azure-sdk-for-java - Release
|
azure-sdk-for-go - Release
|
azure-sdk-for-net - Release
|
azure-sdk-for-js - Release
|
|
@vigaur Hello. Could you solve the ARM's review comments? |
|
@ryansbenson I have resolved all the comments. We are using different objects for input (RecoveryPlanProviderSpecificInput here) and output (RecoveryPlanProviderSpecificDetails here) for many other entities in our code. This is the case since, sometime we may send additional properties in output which may not be present in input (we may add extra properties for recovery plan output which may not be present in input). Also, sometimes for the same property output format may be different than input format. |
ryansbenson
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.
I understand what you're doing, its just going to generate an unusable sdk. The type model for get and put are completely different so there is no way to get, update a single field, put. In your case there would be an entire deep details -> input mapping step needed. I highly suggest you try using your own SDK and decided if you think its acceptable. As this is a common pattern across this your swagger I'll approve it, though please own customer satisfaction for the SDK.
|
re-trigger the CI |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run PrettierCheck |
|
No pipelines are associated with this pull request. |
|
/azp run public.rest-api-specs |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@vigaur Hello. Could you fix errors in PrettierCheck? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run automation - sdk |
|
Azure Pipelines successfully started running 1 pipeline(s). |
* swagger changes for zone to zone recovery plan * zone to zone recovery plan provider specific read only property update * prettier format * prettier formatting
* swagger changes for zone to zone recovery plan * zone to zone recovery plan provider specific read only property update * prettier format * prettier formatting
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.