-
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
Add Provider Share Subscription DTO to include ProviderEmail #7768
Conversation
Automation for azure-sdk-for-pythonThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Automation for azure-sdk-for-goThis PR contains more than 3 context, SDK generation is not enabled. Contexts found:
|
Can one of the admins verify this patch? |
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 fix the error in go package output-folder path
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.
looks good. signing off.
LGTM on go config files |
@prchadal please fix the CI error. Thanks. |
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.
Search changes are fine, since they're just whitespace.
@prchadal I think the "x-ms-discriminator-value" field doesn't need "required" in CI output, maybe I'll need to let ARM review again for the required field. @brjohnstmsft could you review again about these required field? |
@ChenTanyi I only reviewed this for the files that are part of my service (Azure Cognitive Search). I have no context on the rest of the changes. |
@ChenTanyi @brjohnstmsft The required part for discriminator is coming from auto rest valdiation. the oav module before 0.20.0 didnt enforce this condition. looks like the CI for PRs got updated with the latest version of oav. Can you please review this PR with that in perspective? |
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.
@sarajang yeah, I saw the "discriminator" field should be required in CI output, but the field with "x-ms-discriminator-value" doesn't show in it. Therefore, I am wondering whether this field should also be required?
@ravbhatnagar could you review again for the change of required field? Thanks!
...ion/datashare/resource-manager/Microsoft.DataShare/preview/2018-11-01-preview/DataShare.json
Show resolved
Hide resolved
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.
Approved from ARMs side
@ChenTanyi Received ARM sign off, please review for the final merge off. |
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.