-
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
Nithin/action group webhooks with azure active directory integration #6218
Nithin/action group webhooks with azure active directory integration #6218
Conversation
…e directory integration
…are in the response
SDK Automation [Logs] (Generated from 1dca2b0)
|
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-rubyA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-jsA PR has been created for you based on this PR content. Once this PR will be merged, content will be added to your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Can one of the admins verify this patch? |
spell check error is because of specification\mediaservices\resource-manager\Microsoft.Media\stable\2018-07-01\Encoding.json file row 1200 column 95 "specified" is there. This spelling is wrong. This the reason for the failure. We don't own this resource. pls advice |
The spelling issue will be fixed in #6145, sorry for the noise |
@NelsonDaniel . Could you please review this pull request ? |
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 to me. But, requesting ARM feedback since 4 properties were added in Model "WebhookReceiver"
I noticed that person who reviewed #WaitForArmFeedback in an earlier pull request had requested previous API version for easy diff. I am new to the team hence did not add that in the earlier commit message. The prior API version is 2019-03-01. This set of changes is for 2019-06-01. |
@ravbhatnagar , @KrisBash .. could you please review this ? |
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.
LGTM but still waiting for ARM feedback. I will be OOF. I am adding the Reasign label in case this needs to be merged before I am back
@shahabhijeet Could you please review ? |
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.
if ActionGroup_API.json is the new API of your REST spec, would be great if you can add a commit that shows the delta of what got changed in the new API version.
If the only thing that changed is the API version, please provide a detailed description of your PR.
Also we need ARM signOff as this is a new API version.
Having a commit that shows the diff also helps ARM to quickly review your new REST spec.
...fication/monitor/resource-manager/Microsoft.Insights/stable/2019-06-01/actionGroups_API.json
Show resolved
Hide resolved
} | ||
}, | ||
"patch": { | ||
"description": "Updates an existing action group's tags. To update other fields use the CreateOrUpdate method.", |
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.
CreateOrUpdate [](start = 104, length = 14)
Does the PUT of actionGroup allow partial resource body? In other words, does it act like PATCH?
} | ||
}, | ||
"x-ms-pageable": { | ||
"nextLinkName": null |
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.
null [](start = 36, length = 4)
You should set this to "nextLink" even if your service only returns 1 page. Doing so will make adding paging easier for you in the future.
} | ||
}, | ||
"x-ms-pageable": { | ||
"nextLinkName": null |
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.
null [](start = 36, length = 4)
I'd set this to "nextLink" here too even if the service only returns 1 page.
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.
The incremental changes on top of 2019-03-01 look good. I added some comments that you should consider taking, but they are not blocking.
@shahabhijeet Could you please review. Please note ARM team has signed 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.