-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Fix discriminator problem introduced by #8606 #10383
Conversation
Azure Pipelines successfully started running 1 pipeline(s). |
Please do not merge this PR until the corresponding service team had a look at this and approved. |
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-go
|
Azure CLI Extension Generation
|
azure-sdk-for-java
|
azure-sdk-for-net
|
azure-sdk-for-js
|
azure-sdk-for-python
|
azure-sdk-for-python-track2
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
|
Trenton Generation
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 Pipelines successfully started running 1 pipeline(s). |
Looks good, thank you. |
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 think it should be better changed in generator rather than swagger. It is confused to add these three properties, since they are never used.
@ChenTanyi these three fields are |
@njuCZ Since these three fields are exactly same, I don't think they bring any It is just used for fixing the generator bug, but I think generator bug should be fixed by change generator rather than swagger, since changing swagger will affect all SDK which would generate many useless fields. |
Please refer to this PR as reference. This discriminator is by service team's design and exists in all the api-version, not just introduced by this PR. |
This PR fixes the discriminator problem introduced by #8606 which is blocking the SDK upgrade in
terraform-azurerm-provider
- an object has a discriminator but does not have any sub-types.I mimicked the pattern of the swagger in the same RP, introduce three new object:
Nfs3TargetProperties
,ClfsTargetProperties
andUnknownTargetProperties
. They have exactly the same properties asStorageTargetProperties
and just use to serve the discriminator.MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
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 there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.