Skip to content

#ApplicationGateway Ssl Policy, Get AvailableSslOption, Redirect, Azure Websites and backendhealth nic fix#1285

Merged
veronicagg merged 13 commits into
Azure:masterfrom
akshaysngupta:master
Jun 16, 2017
Merged

#ApplicationGateway Ssl Policy, Get AvailableSslOption, Redirect, Azure Websites and backendhealth nic fix#1285
veronicagg merged 13 commits into
Azure:masterfrom
akshaysngupta:master

Conversation

@akshaysngupta
Copy link
Copy Markdown
Member

@akshaysngupta akshaysngupta commented Jun 6, 2017

Summary of Changes

  1. ApplicationGateway Ssl Policy custom cipher suites feature [new properties added to Sslpolicy Property of ApplciationGatewayPropertiesFormat]
  2. Get AvailableSslOption feature [new resource ApplicationGatewayAvailableSslOptions and child resource ApplicationGatewayPredefinedPolicy]
  3. Redirect Configuration feature [new child resource ApplicationGatewayRedirectConfiguration for Application Gateway, new properties in UrlPathMap, PathRules and RequestRoutingRule]
  4. Azure Websites feature [new properties in ApplicationGatewayBackendHttpSettingsPropertiesFormat, ApplicationGatewayProbePropertiesFormat, schema for property ApplicationGatewayProbeHealthResponseMatch]
  5. Backendhealth nic fix [since powershell references NetworkInterfaceIPConfiguration instead of ResourceChild, returning SubResource for NetworkInterfaceIPConfiguration in Swagger created problem]

Information for Validation Issues

We discussed the validation issues for AGW in a previous PR (#1052 (comment)). We are aware of the style issues and will address them in the near future.

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

@msftclas
Copy link
Copy Markdown

msftclas commented Jun 6, 2017

@akshaysngupta,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@azuresdkci
Copy link
Copy Markdown
Contributor

azuresdkci commented Jun 6, 2017

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 90

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/network.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 16

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeFilter.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 14

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

@vishrutshah
Copy link
Copy Markdown
Contributor

Closing and reopening on behalf of Ben Wanner. Thanks

@vishrutshah vishrutshah closed this Jun 9, 2017
@vishrutshah vishrutshah reopened this Jun 9, 2017
@msftclas
Copy link
Copy Markdown

msftclas commented Jun 9, 2017

@akshaysngupta,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 90

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/network.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 16

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeFilter.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 14

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

@msftclas
Copy link
Copy Markdown

msftclas commented Jun 9, 2017

@akshaysngupta,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 90

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/network.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 16

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeFilter.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 14

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

@vishrutshah vishrutshah assigned vishrutshah and unassigned alvadb Jun 15, 2017
"parameters": {
"routeFilterName": "filterName",
"resourceGroupName": "rg1",
"api-version": "2017-03-01",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You should update version in the example to 2017-06-01

"tags": [
"ApplicationGateways"
],
"operationId": "ApplicationGateways_ListAvailableSslPredefinedPolicies",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is this a pageable operation? x-ms-pageable

"description": "Client API version."
},
"PredefinedPolicyNameParameter": {
"name": "predefined-poicy-name",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This does not match the name defined in the path

/subscriptions/{subscriptionId}/providers/Microsoft.Network/applicationGatewayAvailableSslOptions/default/predefinedPolicies/{predefinedPolicyName}

https://travis-ci.org/Azure/azure-rest-api-specs/jobs/241395216#L1165

}
},
"CipherSuitesEnum":{
"type": "string",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

missing description.

Please add for better documentation. https://travis-ci.org/Azure/azure-rest-api-specs/jobs/241395215#L1579

}
}
},
"/subscriptions/{subscriptionId}/providers/Microsoft.Network/applicationGatewayAvailableSslOptions/default": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We'd encourage you to please provide x-ms-examples for the newly introduced operations to help us with model validation.

@vishrutshah
Copy link
Copy Markdown
Contributor

Please also fix the merge conflict for arm-network/compositeNetworkClient.json file

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 99

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/network.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 16

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeFilter.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 14

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

Copy link
Copy Markdown
Contributor

@vishrutshah vishrutshah left a comment

Choose a reason for hiding this comment

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

Please make sure that swagger is semantically correct. https://travis-ci.org/Azure/azure-rest-api-specs/jobs/243447018#L1168

"type": "string",
"description": "Host header to be sent to the backend servers."
},
"pickHostNameFromBackendAddress": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Consider renaming property to hostNameSource and the values could be BackendAddress or Default. Default would be default value. Bools are generally not preferable.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

can't fix.

"type": "string",
"description": "Cookie name to use for the affinity cookie."
},
"probeEnabled": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Consider making this a string enum.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

can't fix.

],
"description": "Backend Address Pool of an application gateway."
},
"ApplicationGatewayBackendHttpSettingsPropertiesFormat": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ConnectionDraining property is missing in this version. What happens when a resource which was created using this property (old api version), is GET using the new API-version which does not have this property? What will the service return?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Connection draining is still there. I just moved it down.

"format": "int32",
"description": "The probe retry count. Backend server is marked down after consecutive probe failure count reaches UnhealthyThreshold. Acceptable values are from 1 second to 20."
},
"pickHostNameFromBackendHttpSettings":{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

consider using string enum

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

can't fix.

},
"description": "Properties of request routing rule of the application gateway."
},
"ApplicationGatewayRequestRoutingRule": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

"type" property is missing. Proxy or non-tracked resources should have the standard name, id and type properties. I th

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

These are child resources for Application Gateway.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

fixed.

},
"description": "Properties of redirect configuration of the application gateway."
},
"ApplicationGatewayRedirectConfiguration": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

type property missing. This is a child resource of ApplicationGateway. Even proxy resources should have the standard name, id and type properties.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

fixed.

"info": {
"title": "NetworkManagementClient",
"description": "The Microsoft Azure Network management API provides a RESTful set of web services that interact with Microsoft Azure Networks service to manage your network resources. The API has entities that capture the relationship between an end user and the Microsoft Azure Networks service.",
"version": "2017-06-01"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are you only changing the api-version of this file? For all other files, its still 2017-03-01 even though they are moved to the 2017-06-01 folder? It would be difficult to review if you add the all the files to a new folder even though nothing has changed.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

version is updated by the team maintaining the resource.

@ravbhatnagar
Copy link
Copy Markdown
Contributor

ARM signs off on the new changes.

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 96

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 35
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 5
Number of linter errors/warnings after the PR: 5

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 96

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 35
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 5
Number of linter errors/warnings after the PR: 5

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

Copy link
Copy Markdown
Contributor

@vishrutshah vishrutshah left a comment

Choose a reason for hiding this comment

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

@ravbhatnagar could you please re-review and make sure things looks good from the ARM perspective. Thanks

"description": "The prefixes that the bgp community contains."
},
"isAuthorizedToUse": {
"isAuthorizedToUse": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are you sure this is a boolean. Because the example depicts it as a string "True" instead of boolean true. https://travis-ci.org/Azure/azure-rest-api-specs/jobs/243501989#L1174

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

These changes came in from master.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@akshaysngupta If the spec is correct, you may need to update the example, if the example is correct, then it's mismatching the spec.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

This was already in master. I just fixed the indentation.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@akshaysngupta I see your point but as @veronicagg mentioned, if you know which one is correct example / service or if you know who is the owner of the service, let's make sure that we understand which one is correct and let's fix that while we have an opportunity here :). Thanks!

Copy link
Copy Markdown
Member Author

@akshaysngupta akshaysngupta Jun 16, 2017

Choose a reason for hiding this comment

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

corrected the example. :)

@azuresdkci
Copy link
Copy Markdown
Contributor

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: arm-network/2017-06-01/swagger/applicationGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 96

File: arm-network/2017-06-01/swagger/checkDnsAvailability.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 6

File: arm-network/2017-06-01/swagger/expressRouteCircuit.json
Number of linter errors/warnings before the PR: 35
Number of linter errors/warnings after the PR: 35

File: arm-network/2017-06-01/swagger/loadBalancer.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 63

File: arm-network/2017-06-01/swagger/networkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 53

File: arm-network/2017-06-01/swagger/networkSecurityGroup.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/networkWatcher.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 30

File: arm-network/2017-06-01/swagger/publicIpAddress.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 49

File: arm-network/2017-06-01/swagger/routeTable.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 55

File: arm-network/2017-06-01/swagger/serviceCommunity.json
Number of linter errors/warnings before the PR: 5
Number of linter errors/warnings after the PR: 5

File: arm-network/2017-06-01/swagger/usage.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 4

File: arm-network/2017-06-01/swagger/virtualNetwork.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 62

File: arm-network/2017-06-01/swagger/virtualNetworkGateway.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 33

File: arm-network/2017-06-01/swagger/vmssNetworkInterface.json
Number of linter errors/warnings before the PR: 0
Number of linter errors/warnings after the PR: 51

Thanks for your co-operation.

@vishrutshah
Copy link
Copy Markdown
Contributor

Thanks a lot @akshaysngupta for the fix. Changes LGTM! I'd still wait until @ravbhatnagar approves this PR :).

@ravbhatnagar
Copy link
Copy Markdown
Contributor

LGTM

@veronicagg veronicagg merged commit 4c5dd5d into Azure:master Jun 16, 2017
@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-python

@AutorestCI
Copy link
Copy Markdown

@olydis
Copy link
Copy Markdown
Contributor

olydis commented Jun 26, 2017

@vishrutshah @akshaysngupta Was vmssPublicIpAddress.json dropped from https://github.com/Azure/azure-rest-api-specs/blob/master/arm-network/compositeNetworkClient.json on purpose? Looks suspicious since vmssPublicIpAddress.json was copied to the new API version folder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.