-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Hub Generated] Review request for Microsoft.AlertsManagement to add version preview/2019-05-05-preview #5750
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
…w/2018-11-02-privatepreview to version 2019-05-05-preview
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
|
Can one of the admins verify this patch? |
changed filters, introduced action rule type and configuration
added more examples and corrected some errors
veronicagg
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.
@roramc there looks to be a syntax error in the swagger file, could you check https://dev.azure.com/azure-sdk/public/_build/results?buildId=21433&view=logs&jobId=5ea8264b-28a6-50c8-6f1c-6d360776db7e&taskId=cb0be435-f7f1-5f7a-37e4-9cbab5376524&lineStart=19&lineEnd=20&colStart=1&colEnd=1 ?
|
Tagging @KrisBash who was looking at the original PR from ARM side. |
fixing swagger synatax error
fixing patch operation
fixing few model validation issues
corrected incorrect variables in examples
changing parameter in examples
fixed the syntax issue/model validation, etc. |
|
Please review errors at https://portal.azure-devex-tools.com/app/branch/roramc/azure-rest-api-specs/dev-alertsmanagement-Microsoft.AlertsManagement-2019-05-05-preview...master/linter particularly the ones under "IsNew" column = true. |
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.
minor: we generally use 2 spaces for indentation. See pointer to other CI errors above.
fixing resource group parameter error
|
@roramc please follow up with the ARM team on signing off for this PR, since they haven't replied here yet. Regarding your question on removing existing resource types from swagger and examples, if they are part of the service you're specifying they should remain there, why would you remove them? thanks! |
The other resource types are already in GA. So we were thinking of just having the new resource type with the preview version. Not sure what is the convention around this. |
KrisBash
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.
LGTM
fixed few linter warnings
veronicagg
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.
left one more question inline, rest looks good. thanks!
| "schema": { | ||
| "$ref": "#/definitions/smartGroupsList", | ||
| "description": "List of smart groups in value property." | ||
| "$ref": "#/definitions/smartGroupsList" |
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.
names for model definitions should be capitalized for consistency, I noticed you have some starting with lower case and some upper case in the "definitions" section.
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.
Done
Changed models to upper case
…-05-preview' of https://github.com/roramc/azure-rest-api-specs into dev-alertsmanagement-Microsoft.AlertsManagement-2019-05-05-preview
fixing duplicate issues due to merge conflicts
veronicagg
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.
@roramc Thanks for addressing the comments!
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: