Skip to content

Conversation

@abhinav-ghai
Copy link
Member

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Oct 27, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@@ -0,0 +1,25 @@
{
"parameters": {
"subscriptionId": "mySubscriptionId",

Choose a reason for hiding this comment

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

Minor: Have a guid for subscriptionId example

"SoftwareProperties": {
"description": "Properties of the software object.",
"properties": {
"name": {

Choose a reason for hiding this comment

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

are all the properties required?

Copy link
Member Author

Choose a reason for hiding this comment

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

This is the contract we are giving in the View model of user so we have to specify all the properties we plan on exposing.

}
},
"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachines/{vmName}/providers/Microsoft.GuestConfiguration/software/{softwareId}": {
"get": {

Choose a reason for hiding this comment

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

get [](start = 7, length = 3)

Would extension resource be cached in the future, please confirm with ARM team? Basically the pattern of exposing only GET without creating actual ARM resource, would that cause any problem. Are there other RP using this pattern?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks, I am checking this with some one from ARM team.

@hovsepm
Copy link
Contributor

hovsepm commented Oct 31, 2018

@sourabhguha @AnatoliB @nitinbps please approve this PR when you are done with the review.

Copy link

@nitinbps nitinbps left a comment

Choose a reason for hiding this comment

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

:shipit:

@hovsepm hovsepm merged commit d4365e6 into Azure:master Oct 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants