Skip to content

Conversation

@roramc
Copy link
Contributor

@roramc roramc commented Apr 24, 2019

If you are a MSFT employee you can view your work branch via this link.

Contribution checklist:

@AutorestCI
Copy link

AutorestCI commented Apr 24, 2019

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Apr 24, 2019

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3723

@AutorestCI
Copy link

AutorestCI commented Apr 24, 2019

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Apr 24, 2019

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented Apr 24, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

changed filters, introduced action rule type  and configuration
added more examples and corrected some errors
Copy link
Contributor

@veronicagg veronicagg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@veronicagg veronicagg added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Apr 25, 2019
@veronicagg
Copy link
Contributor

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
@roramc
Copy link
Contributor Author

roramc commented Apr 25, 2019

Copy link
Contributor

@veronicagg veronicagg left a 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
Copy link
Contributor Author

roramc commented Apr 26, 2019

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.
Property names like https://github.com/roramc/azure-rest-api-specs/blob/48467c63614bb04de4535ee9da6db3a232089714/specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/preview/2019-05-05-preview/AlertsManagement.json#L1687 should be camel cased without spaces.
Please check error generating Python SDK https://dev.azure.com/azure-sdk/public/_build/results?buildId=22034&view=logs&jobId=957f396e-b28a-53c4-b5bb-b8c6d959bd2d&taskId=142feabb-6d02-5968-caa1-f5b3c04c5cae&lineStart=136&lineEnd=137&colStart=1&colEnd=1

I have fixed most of the lint errors, the camel case error are for the contract of an existing resource type and existing version. So I can't change those properties. Also, we are just adding one new resource type for this version, should I remove the other existing resource types from the swagger and examples?

@veronicagg
Copy link
Contributor

@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!

@roramc
Copy link
Contributor Author

roramc commented Apr 29, 2019

@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.

@roramc roramc closed this Apr 29, 2019
@roramc roramc reopened this Apr 30, 2019
Copy link
Contributor

@KrisBash KrisBash left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@KrisBash KrisBash added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Apr 30, 2019
roramcmsft and others added 2 commits May 1, 2019 20:43
Copy link
Contributor

@veronicagg veronicagg left a 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"
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

roramcmsft added 3 commits May 2, 2019 10:39
Changed models to upper case
fixing duplicate issues due to merge conflicts
Copy link
Contributor

@veronicagg veronicagg left a 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!

@veronicagg veronicagg merged commit 56de8e7 into Azure:master May 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants