[Azure Automation] Swagger json files for rest of 15 resources and and changes to by fearthecowboy · Pull Request #1045 · Azure/azure-rest-api-specs

fearthecowboy · 2017-03-17T17:12:42Z

Re-Creating PR for @vivlingaiah

@vivlingaiah -- You need to complete the following checklist, and fix the conflicts between the master branch and this PR (Pull from master into your local branch, fix the changes and push back into your fork on AzureAutomationTeam:master

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

I have read the contribution guidelines.
My spec meets the review criteria:
- The spec conforms to the Swagger 2.0 specification.
- Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
- The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

Starting with these 4 resources. json files are split by each resource. rest of resources to come subsequently.

… for now

…d changes to account.json

vishrutshah

I've only reviewed arm-automation/2015-10-31/swagger/account.json from the PR so far

vishrutshah · 2017-03-18T21:42:47Z

+              "$ref": "#/definitions/AutomationAccount"
+            }
+          },
+		  "default": {


correct indentation

all indentations are corrected now.

vishrutshah · 2017-03-18T21:43:31Z

+        ],
+        "responses": {
+          "200": {
+            "description": "OK",


please provide descriptive descriptions

Hi Vishrut,
We have received exceptions for the below issues:
[Azure Automation] validations (size, range, regexes) on properties and parameters missing #1020
#1020
[Azure Automation] Descriptions need to be corrected in all Azure Automation resources #1021
#1021

Samer is aware of above issues. The two issues above will be revisited. These descriptions were inherited from Hyak specs and we won't be changing descriptions or validation regex at the moment
Leave a comment

vishrutshah · 2017-03-18T21:44:40Z

+            "in": "body",
+            "required": true,
+            "schema": {
+				"$ref": "#/definitions/AutomationAccountCreateOrUpdateParameters"


indentation

vishrutshah · 2017-03-18T21:45:56Z

+          }
+        }
+      },
+      "put": {


Is this a long-running operation?

vishrutshah · 2017-03-18T21:47:05Z

+              "$ref": "#/definitions/AutomationAccount"
+            }
+          },
+		  "default": {


indentation

vishrutshah · 2017-03-18T22:27:06Z

+    },
+	"Usage": {
+      "properties": {
+        "id": {


readOnly?

vishrutshah · 2017-03-18T22:28:08Z

+        },
+        "unit": {
+          "type": "string",
+          "description": "Gets or sets the usage unit name."


please provide descriptive description so that users can understand this property. Applies for entire document.

Leave a commentHi Vishrut,
We have received exceptions for the below issues:
[Azure Automation] validations (size, range, regexes) on properties and parameters missing #1020
#1020
[Azure Automation] Descriptions need to be corrected in all Azure Automation resources #1021
#1021

Samer is aware of above issues. The two issues above will be revisited. These descriptions were inherited from Hyak specs and we won't be changing descriptions or validation regex at the moment

vishrutshah · 2017-03-18T22:39:48Z

+          "description": "Gets or sets the current usage value."
+        },
+        "limit": {
+          "type": "integer",


you should use Minimum and Maximum constrains here

Leave a commentHi Vishrut,
We have received exceptions for the below issues:
[Azure Automation] validations (size, range, regexes) on properties and parameters missing #1020
#1020
[Azure Automation] Descriptions need to be corrected in all Azure Automation resources #1021
#1021

Samer is aware of above issues. The two issues above will be revisited. These descriptions were inherited from Hyak specs and we won't be changing descriptions or validation regex at the moment

vishrutshah · 2017-03-18T22:40:16Z

+      "in": "path",
+      "required": true,
+      "type": "string",
+      "description": "Gets subscription credentials which uniquely identify Microsoft Azure subscription. The subscription ID forms part of the URI for every service call."


Hi Vishrut,
We have received exceptions for the below issues:
[Azure Automation] validations (size, range, regexes) on properties and parameters missing #1020
#1020
[Azure Automation] Descriptions need to be corrected in all Azure Automation resources #1021
#1021

Samer is aware of above issues. The two issues above will be revisited. These descriptions were inherited from Hyak specs and we won't be changing descriptions or validation regex at the moment

Yes @vishrutshah they have exceptions for fixing descriptions

vishrutshah · 2017-03-18T22:40:31Z

+      "in": "path",
+      "required": true,
+      "type": "string",
+	  "pattern": "^[-\\w\\._]+$",


Indentation

vishrutshah · 2017-03-18T22:44:29Z

I'd request you please provide x-ms-example for your APIs. https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/x-ms-examples.md

viveklingaiah · 2017-03-20T19:18:21Z

Hi Vishrut,
We have received exceptions for the below issues:
[Azure Automation] validations (size, range, regexes) on properties and parameters missing #1020
#1020
[Azure Automation] Descriptions need to be corrected in all Azure Automation resources #1021
#1021

Samer is aware of above issues. The two issues above will be revisited. These descriptions were inherited from Hyak specs and we won't be changing descriptions or validation regex at the moment

viveklingaiah · 2017-03-20T20:13:30Z

More importantly, I need help your help with below issues.
Issue 1:
couple of operations need to automatically generate new Guid each time. Is there a way to do it in Swagger ? This swagger was auto-generated using Hyak specs. Could you confirm this is correct way to auto-generate new guid on each invocation of operation ?

viveklingaiah · 2017-03-20T20:19:11Z

Issue 2: The issue is AutoRest command that generates “Generated” files adds member Credentials (Credentials needed for the client to connect to Azure.) Co-Incidentally, we also have an API “Credentials” due to which two members have name conflicts. Could you let us know how to resolve this issue? I’ve attached the concerned files for your reference. (Forwarded the .cs files in reference to Vishrut). There is a name conflict. Two "Credentials" can be found

vishrutshah · 2017-03-20T22:43:17Z

#Issue 2 is coming from https://github.com/Azure/azure-rest-api-specs/pull/1045/files#diff-bf0e1b6e54180951dd6138234a55f3c4R239 : operationId should be PsCredentials_List.

vishrutshah · 2017-03-20T22:47:04Z

Issue 1: Yes AutoRest should generate guid for you. Ref: Azure/autorest#784

salameer · 2017-03-20T23:04:56Z

@vivlingaiah just to be clear xms-examples are not covered in the exceptions, just wanted to make sure that we're on the same page here

vishrutshah

Reviewed arm-automation/2015-10-31/swagger/certificate.json. Please fix indentation across the swagger files

vishrutshah · 2017-03-20T22:57:49Z

+        ],
+        "responses": {
+          "200": {
+            "description": "OK"


The PUT/GET/PATCH operations must have same schema response - I see patch is not returning Certificate.

vishrutshah · 2017-03-20T22:58:42Z

+        "tags": [
+          "Certificates"
+        ],
+        "operationId": "Certificates_List",


_ListByAutomationAccounts?

vishrutshah · 2017-03-20T22:59:33Z

+      "properties": {
+        "base64Value": {
+          "type": "string",
+          "description": "Gets or sets the base64 encoded value of the certificate."


Gets or Sets MUST not appear in entire swagger.

vishrutshah · 2017-03-20T23:00:10Z

+          "type": "string",
+          "description": "Gets or sets the thumbprint of the certificate."
+        },
+        "isExportable": {


Is this readOnly?

vishrutshah · 2017-03-20T23:00:13Z

+          "type": "string",
+          "description": "Gets or sets the description of the certificate."
+        },
+        "thumbprint": {


Is this readOnly?

vishrutshah · 2017-03-20T23:01:11Z

+          "type": "string",
+          "description": "Gets or sets the thumbprint of the certificate."
+        },
+        "expiryTime": {


Is this updatable?

vishrutshah · 2017-03-20T23:01:24Z

+          "type": "boolean",
+          "description": "Gets or sets the is exportable flag of the certificate."
+        },
+        "creationTime": {


vishrutshah · 2017-03-20T23:01:30Z

+          "format": "date-time",
+          "description": "Gets or sets the creation time."
+        },
+        "lastModifiedTime": {


vishrutshah · 2017-03-20T23:01:57Z

+        },
+        "lastModifiedTime": {
+          "type": "string",
+          "format": "date-time",


What is the date-time format? ISO8601?

vishrutshah · 2017-03-20T23:02:30Z

+      },
+      "description": "Properties of the certificate."
+    },
+    "Certificate": {


Is this a tracked resource?

vishrutshah

Reviewed arm-automation/2015-10-31/swagger/connection.json. Please update indentation and provide accurate descriptions.

Also please provide x-ms-example for each of the operation

vishrutshah · 2017-03-20T23:15:10Z

+        ],
+        "responses": {
+          "200": {
+            "description": "OK"


Patch MUST return #/definitions/Connection schema

vishrutshah · 2017-03-20T23:15:41Z

+        "tags": [
+          "Connections"
+        ],
+        "operationId": "Connections_List",


_ListByAutomationAccounts

vishrutshah · 2017-03-20T23:17:30Z

+        }
+      }
+    },
+    "/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccount}/connections": {


Don't you have

List - BySubscription &
ListByResourceGroup for this tracked resource?

this is not a tracked resource. corrected naming of methods

vishrutshah · 2017-03-20T23:41:04Z

+        },
+        "connectionType": {
+          "$ref": "#/definitions/ConnectionTypeAssociationProperty",
+          "description": "Gets or sets the connectionType of the connection."


Gets or Sets MUST not appear in the swagger. Documentation will not be good.

vishrutshah · 2017-03-20T23:41:43Z

+          "description": "Gets or sets the field definition values of the connection."
+        },
+        "creationTime": {
+          "type": "string",


vishrutshah · 2017-03-20T23:41:48Z

+          "format": "date-time",
+          "description": "Gets or sets the creation time."
+        },
+        "lastModifiedTime": {


vishrutshah · 2017-03-20T23:42:39Z

+      },
+      "description": "Definition of the connection properties."
+    },
+    "Connection": {


Is this a tracked/Proxy Resource? Should it inherit from the common Resource model having id, name, type as readOnly?

this is not a tracked resource

vishrutshah · 2017-03-20T23:42:51Z

+    "Connection": {
+      "properties": {
+        "id": {
+          "type": "string",


vishrutshah · 2017-03-21T01:08:15Z

+        }
+      }
+    },
+	"/{subscriptionId}/operations/{requestId}": {


Is this the API supported & maintained by your team?

it's not supported. I removed it

vishrutshah · 2017-03-21T01:09:11Z

+          }
+        ],
+        "responses": {
+          "201": {


when do you return 201 v/s 200? Seems like both return the same model?

sarangan12 · 2017-04-03T16:39:54Z

The following operation names are violating the rules:

Statistics_ListByAutomationAccount
Usages_ListByAutomationAccount
Certificates_ListByAutomationAccount
Connections_ListByAutomationAccount
ConnectionTypes_ListByAutomationAccount
PsCredentials_ListByAutomationAccount
Jobs_ListByAutomationAccount
JobStreams_ListByJob
Activities_ListByModule
Modules_ListByAutomationAccount
Fields_ListByType
Runbooks_ListByAutomationAccount
TestJobStreams_ListByTestJob
Schedules_ListByAutomationAccount
JobSchedules_ListByAutomationAccount
Variables_ListByAutomationAccount
Webhooks_ListByAutomationAccount
CompilationJobs_ListByAutomationAccount
Configurations_ListByAutomationAccount
Nodes_ListByAutomationAccount
NodeReports_ListByNode
NodeConfigurations_ListByAutomationAccount
HybridRunbookWorkerGroups_ListByAutomationAccount

@vivlingaiah Can you confirm if you have exceptions approved for all of these?

sarangan12 · 2017-04-03T16:48:37Z

A body parameter must be named 'parameters'. The following paths are violating the rule:

Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/patch/parameters[3]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/put/parameters[3]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/certificates/{certificateName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/connections/{connectionName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/connections/{connectionName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/connectionTypes/{connectionTypeName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/modules/{moduleName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/modules/{moduleName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runbooks/{runbookName}/draft/content/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runbooks/{runbookName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runbooks/{runbookName}/draft/testJob/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/schedules/{scheduleName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/schedules/{scheduleName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/jobSchedules/{jobScheduleId}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/variables/{variableName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/variables/{variableName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/webhooks/{webhookName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/compilationjobs/{compilationJobId}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/agentRegistrationInformation/regenerateKey/post/parameters[3]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/nodeConfigurations/{nodeConfigurationName}/put/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/certificates/{certificateName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/credentials/{credentialName}/put/parameters[4]
24: Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/credentials/{credentialName}/patch/parameters[4]
Path: #/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runbooks/{runbookName}/patch/parameters[4]

sarangan12 · 2017-04-03T16:56:51Z

One of the rule is that "Parameters "subscriptionId" and "api-version" are not allowed in the operations section, define these in the global parameters section instead". There are several paths which violate the rule: https://gist.github.com/sarangan12/e5ffe03d76cbaccbcceba2060c2dec8d#file-gistfile1-txt

sarangan12 · 2017-04-03T16:57:17Z

ERROR: A 'POST' operation 'RunbookDraft_Publish' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201 or 204.
Path: file:///C:/workspace/azure-rest-api-specs/arm-automation/compositeAutomation.json#/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runbooks/{runbookName}/draft/publish/post/extensions/x-ms-long-running-operation

sarangan12 · 2017-04-03T16:57:31Z

ERROR: The property 'odata.nextLink' specified by nextLinkName does not exist in the 200 response schema.
Path: file:///C:/workspace/azure-rest-api-specs/arm-automation/compositeAutomation.json#/paths/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/hybridRunbookWorkerGroups/get/extensions/x-ms-pageable

sarangan12 · 2017-04-03T16:57:46Z

ERROR: Tracked Resource failing validation is: "DscConfiguration". Validation Failed: 2.
A Tracked Resource must have:
1. A Get Operation
2. A ListByResourceGroup operation with x-ms-pageable extension and
3. A ListBySubscriptionId operation with x-ms-pageable extension.
4. "type","location","tags" should not be used in the RP property bag named "properties".
Path: file:///C:/workspace/azure-rest-api-specs/arm-automation/compositeAutomation.json#/definitions
ERROR: Tracked resource 'DscConfiguration' must have patch operation that at least supports the update of tags.
Path: file:///C:/workspace/azure-rest-api-specs/arm-automation/compositeAutomation.json#/definitions

…r resource ids

viveklingaiah · 2017-04-03T23:20:07Z

Hi Sarangan,

Addressed your feedback
Changed plural name to singular. AutomationAccounts_ to AutomationAccount_ for all resources
renamed all parameters to "parameters"
For 9 resources, please note validation of x-ms-examples will have errors such as (returned null) for which I have created an issue [Azure Automation] Service returns null values for few resources. validation of x-ms-examples fails. #1091 Samer advised to create an issue at this point to unblock us

…ublish

Dismissing. Assigned to me

AutorestCI · 2017-04-06T22:04:04Z

No modification for Ruby

AutorestCI · 2017-04-06T22:04:25Z

No modification for Ruby

AutorestCI · 2017-04-06T22:04:29Z

No modification for Python

AutorestCI · 2017-04-06T22:04:42Z

No modification for NodeJS

viveklingaiah added 14 commits February 17, 2017 16:48

Swagger json files for accounts, runbooks, jobs and modules

7f3cbe4

Starting with these 4 resources. json files are split by each resource. rest of resources to come subsequently.

Added missing commas after Linter validation failures

779a694

Removed "Standard" and "Premium" with Sku definition

404077e

Created composite swagger json file and renamed file

a83b925

Corrected job.json Swagger file

edb96ec

Including only account.json. Resolved errors. Removed other resources…

ba72c98

… for now

Removed duplicate operationId AutomationAccounts_Patch

ac72df3

Fixed warnings related to description

cc5fe08

changes after suggested changes from Garrett

d5a5fd0

added missing default responses

85f7874

added missing validations for string inputs

79dbe87

Removed regex validation and added "Gets or Sets" for definitions

e21792c

Capitalized Sku to SKU in description and changed a missing description

f6a4359

[Azure Automation] Swagger json files for rest of 15 resources and an…

af22420

…d changes to account.json

msftclas added the cla-not-required label Mar 17, 2017

azuresdkci assigned sergey-shandar Mar 17, 2017

salameer assigned vishrutshah and unassigned sergey-shandar Mar 17, 2017

vishrutshah suggested changes Mar 18, 2017

View reviewed changes

vishrutshah suggested changes Mar 20, 2017

View reviewed changes

vishrutshah previously requested changes Mar 21, 2017

View reviewed changes

vishrutshah assigned sarangan12 Mar 21, 2017

olydis mentioned this pull request Apr 3, 2017

[Azure Automation] Deserializing fails with SafeJsonConvert.DeserializeObject Azure/autorest#2103

Closed

Adding x-ms-examples, removed subscription ids/account names and othe…

b54e494

…r resource ids

viveklingaiah force-pushed the master branch 2 times, most recently from 0552348 to e4dc90d Compare April 3, 2017 23:15

Merge conflict resolution for account.json and fix for RunbookDraft_P…

78c896e

…ublish

viveklingaiah force-pushed the master branch from e4dc90d to 78c896e Compare April 4, 2017 19:50

viveklingaiah added 2 commits April 4, 2017 13:44

Fixed Get Job stream deserialization error

1dd67d7

Renamed body parameters testJobCreateParameters to parameters

904bd38

sarangan12 approved these changes Apr 4, 2017

View reviewed changes

Fixing Runbook Draft create operation

1944b55

sarangan12 approved these changes Apr 5, 2017

View reviewed changes

Fixed json validation errors with string response body example files

e90ae9c

viveklingaiah force-pushed the master branch from ec241f3 to e90ae9c Compare April 6, 2017 21:09

Moved empty definitions, parameters outside paths in credential.json

c0f4f6d

sarangan12 approved these changes Apr 6, 2017

View reviewed changes

sarangan12 merged commit 84aaf9c into Azure:master Apr 6, 2017

vishrutshah mentioned this pull request Apr 18, 2017

[Automation] Correct the provided x-ms-examples #1133

Open

Conversation

fearthecowboy commented Mar 17, 2017 • edited by azuresdkci Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR information

Quality of Swagger

Uh oh!

vishrutshah left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vishrutshah commented Mar 18, 2017

Uh oh!

viveklingaiah commented Mar 20, 2017

Uh oh!

viveklingaiah commented Mar 20, 2017

Uh oh!

viveklingaiah commented Mar 20, 2017

Uh oh!

vishrutshah commented Mar 20, 2017

Uh oh!

vishrutshah commented Mar 20, 2017

Uh oh!

salameer commented Mar 20, 2017

Uh oh!

vishrutshah left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

fearthecowboy commented Mar 17, 2017 •

edited by azuresdkci

Loading

vishrutshah left a comment •

edited

Loading