Add Azure SQL Database Failover Group REST API specs by btasdoven · Pull Request #1079 · Azure/azure-rest-api-specs

btasdoven · 2017-03-29T04:58:19Z

Adding Azure SQL Database Failover Group REST API specifications as the feature will be in public preview soon.

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.
- The spec follows the guidelines described in the Swagger checklist document.
- Validation tools were run on swagger spec(s) and have all been fixed in this PR.

msftclas · 2017-03-29T04:58:23Z

@btasdoven,
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

jaredmoo · 2017-03-29T18:14:25Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "default": {
+                        "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout.",
+                        "schema": {
+                            "$ref": "#/definitions/ArmErrorResponseMessage"


Remove this

jaredmoo · 2017-03-29T18:14:51Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                "tags": [
+                    "FailoverGroups"
+                ],
+                "description": "Creates or updates the failover group with the given name.",


Creates or updates a failover group .

jaredmoo · 2017-03-29T18:15:07Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                "tags": [
+                    "FailoverGroups"
+                ],
+                "description": "Deletes the failover group with the given name.",


Deletes a failover group.

jaredmoo · 2017-03-29T18:15:15Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "default": {
+                        "description": "*** Error Responses: ***\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabases - The provided databases in the request are not valid database resource IDs.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidPartner - The given partners field in create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupCreateOrUpdateRequestDuplicatePartner - One or more of the provided partner servers are already part of the failover group. Please make sure the primary server and all of the given partner servers are unique.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidDatabaseServer - One or more of the provided databases do not exist on the primary server of the failover group. Please make sure that all the databases exist on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestUnsupportedPartnerCount - Only one partner server is supported.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpoint - The readWriteEndpoint field is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalid - The create or update failover group request body is empty or invalid.\n\n * 400 FailoverGroupUpdateOrDeleteRequestOnSecondary - Modifications to the failover group are not allowed on a secondary server. Execute the request on the primary server.\n\n * 400 FailoverGroupCreateOrUpdateRequestNegativeGracePeriodValues - Grace period value for the read-write endpoint must be non-negative.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFields - The property failoverWithDataLossGracePeriodMinutes must be provided when failover policy Automatic is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteFailoverPolicy - The failoverPolicy field for the read-write endpoint is required for create or update requests.\n\n * 400 FailoverGroupCreateOrUpdateRequestInvalidReadWriteEndpointFieldsForManualPolicy - Grace period value should not be provided when failover policy Manual is selected for the read-write endpoint.\n\n * 400 FailoverGroupCreateOrUpdateRequestReadOnlyPropertyModified - The create or update failover group request body should not modify the read-only property '{0}'.\n\n * 400 FailoverGroupFailoverRequestOnPrimary - The failover request should be initiated on the secondary server of failover group.\n\n * 400 FailoverGroupPartnerServerFromDifferentSubscription - Primary server and the partner servers of failover group are from different subscriptions. Cross subscription for servers of failover group is not allowed.\n\n * 400 UnableToResolveRemoteServer - The remote partner server name could not be resolved due to an invalid server name or DNS connectivity issues.\n\n * 400 RemoteDatabaseCopyPermission - User does not have sufficient permission to create a database copy on the specified server.\n\n * 400 InvalidFailoverGroupRegion - Servers specified in a Failover Group need to reside in different regions to provide isolation.\n\n * 400 ServerNotFound - The requested server was not found.\n\n * 400 FailoverGroupDoesNotExist - Failover group does not exist on a server.\n\n * 400 FailoverGroupNotSecondary - Failover cannot be initiated from the primary server in a Failover Group.\n\n * 400 PlannedFailoverTimedOutForDatabase - User invoked planned failover, it timed out, and a specific database appears to be to blame.\n\n * 400 PlannedFailoverTimedOut - User invoked planned failover, and it timed out while trying to contact the partner management service.\n\n * 400 DatabaseInFailoverGroupNotPrimary - GeoDR link for the database already exists, but its role is not 'Primary' or it is not continuous copy link.\n\n * 400 InvalidAddSecondaryPermission - User does not have sufficient permission to add secondary on the specified server.\n\n * 400 InvalidSku - The user specified an invalid sku.\n\n * 400 FeatureDisabledOnSelectedEdition - User attempted to use a feature which is disabled on current database edition.\n\n * 400 InvalidTargetSubregion - The target server of a non-readable secondary is not in a DR paired Azure region.\n\n * 400 PartnerServerNotCompetible - The user is attempting to copy a database from a SAWA V1 server to a Sterling server or vice versa.\n\n * 400 IncorrectReplicationLinkState - The operation expects the database to be in an expected state on the replication link.\n\n * 400 ResourcePoolNotFound - Specified elastic pool does not exist in the specified logical server.\n\n * 400 GeoReplicationDatabaseNotSecondary - The operation expects the database to be a replication target.\n\n * 400 GeoReplicaLimitReached - The per-replica replication limit was reached.\n\n * 400 FailoverGroupCreateOrUpdatePartiallySucceeded - Some databases could not be added or removed.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ResourceNotFound - The requested resource was not found.\n\n * 404 OperationIdNotFound - The operation with Id does not exist.\n\n * 404 ServerNotInSubscriptionResourceGroup - Specified server does not exist in the specified resource group and subscription.\n\n * 404 SourceDatabaseNotFound - The source database does not exist.\n\n * 404 ServerNotInSubscription - Specified server does not exist on the specified subscription.\n\n * 405 UnsupportedReplicationOperation - An unsupported replication operation was initiated on the database.\n\n * 409 OperationCancelled - The operation has been cancelled by user.\n\n * 409 OperationInterrupted - The operation on the resource could not be completed because it was interrupted by another operation on the same resource.\n\n * 409 UpdateSloInProgress - User tried to initiate an incompatible operation while a SLO update was in progress.\n\n * 409 RemoteDatabaseExists - The destination database name already exists on the destination server.\n\n * 409 FailoverGroupAlreadyExists - Failover group already exists on a given server.\n\n * 409 FailoverGroupBusy - Failover Group is busy with another operation.\n\n * 409 DatabaseBelongsToOtherFailoverGroup - Database belongs to other Failover Group and cannot be consider a part of this one.\n\n * 409 DatabaseBeingAddedToFailoverGroup - The database is currently being added to Failover Group, customer needs to wait for this operation to finish to issue remove.\n\n * 409 DatabaseBeingRemovedFromFailoverGroup - The database is currently being removed from failover group, customer needs to wait for this operation to finish to issue add.\n\n * 409 FailoverGroupDnsRecordInUse - A duplicate DNS record exists for the requested endpoint.\n\n * 409 InvalidFailoverGroupName - Invalid Failover Group name was supplied.\n\n * 409 SubscriptionDisabled - Subscription is disabled.\n\n * 409 ConflictingSystemOperationInProgress - A system maintenance operation is in progress on the database and further operations need to wait until it is completed.\n\n * 409 InvalidOperationForDatabaseNotInReplicationRelationship - A replication seeding operation was performed on a database that is already in a replication relationship.\n\n * 409 InvalidDatabaseStateForOperation - The operation is not allowed on the database in its current replication state.\n\n * 409 DuplicateGeoDrRelation - The databases are already in a replication relation. This is a duplicate request.\n\n * 409 GeoReplicationCannotBecomePrimaryDuringUndo - User attempted to failover or force-terminate a geo-link while the secondary is in a state where it may not be physically consistent and so cannot enter the primary role.\n\n * 409 FailoverGroupUnableToPerformGroupOperationOnDatabases - The list of databases to add/remove to/from Failover Group contains errors that are preventing operation to complete.\n\n * 429 SubscriptionTooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 ConflictingServerOperation - An operation is currently in progress for the server.\n\n * 429 TooManyRequests - Requests beyond max requests that can be processed by available resources.\n\n * 429 SubscriptionTooManyCreateUpdateRequests - Requests beyond max requests that can be processed by available resources.\n\n * 500 OperationTimedOut - The operation timed out and automatically rolled back. Please retry the operation.\n\n * 504 RequestTimeout - Service request exceeded the allowed timeout.",
+                        "schema": {
+                            "$ref": "#/definitions/ArmErrorResponseMessage"


jaredmoo · 2017-03-29T18:15:41Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                "tags": [
+                    "FailoverGroups"
+                ],
+                "description": "Gets the failover group with the given name.",


Gets a failover group.

jaredmoo · 2017-03-29T18:26:03Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "description": "Read-only endpoint of the failover group instance."
+                },
+                "replicationRole": {
+                    "description": "Local replication role of the failover group instance.",


jaredmoo · 2017-03-29T18:26:21Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "type": "string"
+                },
+                "partnerServers": {
+                    "description": "List of partner server information for the failover group.",


jaredmoo · 2017-03-29T18:26:55Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "enum": [
+                        "Manual",
+                        "Automatic"
+                    ],


Needs x-ms-enum. See https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/creating-swagger.md#Enum-x-ms-enum

jaredmoo · 2017-03-29T18:40:10Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                    "enum": [
+                        "Primary",
+                        "Secondary"
+                    ],


Need x-ms-enum

jaredmoo · 2017-03-29T18:40:46Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+                }
+            }
+        },
+        "FailoverGroupResourceList": {


FailoverGroupList

dsgouda · 2017-03-29T22:36:07Z

I shall take a look at this soon

dsgouda · 2017-03-29T23:26:14Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+  "produces": [
+    "application/json"
+  ],
+  "paths": {


Please expose an /operations API for this spec

Hey @dsgouda , I was told by @veronicagg that /operations isn't needed in each swagger file - it's just needed once per RP. #1005 (comment)

That's correct, if there is an operations API already existing which returns the operations mentioned in this spec, you can disregard this comment

dsgouda · 2017-03-29T23:26:58Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+        },
+        "parameters": [
+          {
+            "$ref": "#/parameters/SubscriptionIdParameter"


nit: For consistency, put SubscriptionId and ApiVersion together at the beginning or at the end of the parameters section

Also applies here, here, here, here, here, here and here

dsgouda · 2017-03-29T23:31:06Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+      "type": "object",
+      "properties": {
+        "failoverPolicy": {
+          "description": "Failover policy of the read-write endpoint for the failover group.",


Consider marking this as "modelAsString": true if the enum is expected to change in the future, not doing so causes breaking changes

Linked here, here and here

dsgouda · 2017-03-29T23:35:55Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+    "FailoverGroupProperties": {
+      "description": "Properties of a failover group.",
+      "type": "object",
+      "properties": {


Some properties here look like candidates for readonly properties, please verify if you have all properties correctly marked as readonly

Linked here and here

We allow customers to update those fields. I made a second pass on them to make sure all the read-only properties are marked as read only.

Just curious, is FailoverGroupReadWriteEndpoint some sort of a url?

dsgouda · 2017-03-29T23:36:48Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+      },
+      "x-ms-azure-resource": true
+    },
+    "TrackedResource": {


nit: If you're not using this, you can remove it

I can't correctly see which lines you comment on @dsgouda . This and all of the next comments are for the line 321. Any ideas to view them?

Weird, I might have to try this manually, let me get back in a while

Linked here

dsgouda · 2017-03-29T23:41:07Z

arm-sql/2015-05-01-preview/swagger/failoverGroups.json

+          ],
+          "description": "Resource tags."
+        },
+        "properties": {


Consider using x-ms-client-flatten here for the nested properties for better user experience

Linked here

dsgouda · 2017-03-30T18:33:34Z

Github is probably acting up because of the super long description for one of the operation responses, I've tried my best to link my comments to the line numbers, hope that helps

dsgouda · 2017-03-30T20:19:18Z

Linter rules look good, generated C# code seems to compile too. LGTM

AutorestCI · 2017-03-30T20:24:44Z

No modification for NodeJS

AutorestCI · 2017-03-30T20:24:50Z

Azure/azure-sdk-for-python#1058

AutorestCI · 2017-03-30T20:25:44Z

Azure/azure-sdk-for-ruby#738

* New Falcon Resource Provider APIs * Address GO SDK failure * Remove unused example file * Addressed PR comments * Addressed PR comment about long-running-operation

btasdoven added 2 commits March 28, 2017 21:30

Add Failover Group REST API specs

6fc6d26

Add Failover Group REST API specs

27fbb6e

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

azuresdkci assigned dsgouda Mar 29, 2017

btasdoven added 2 commits March 28, 2017 23:54

Fixing linter errors

983b582

Fix subscriptionId and resourceGroup parameter descriptions

f311a27

jaredmoo suggested changes Mar 29, 2017

View reviewed changes

addressed Jared's comments

141878f

dsgouda suggested changes Mar 29, 2017

View reviewed changes

minor fixes to address comments

8a0893f

dsgouda approved these changes Mar 30, 2017

View reviewed changes

dsgouda merged commit 29bd2d0 into Azure:master Mar 30, 2017

AutorestCI mentioned this pull request Mar 30, 2017

[SQL] Add Azure SQL Database Failover Group REST API specs Azure/azure-sdk-for-python#1058

Closed

AutorestCI mentioned this pull request Mar 30, 2017

Automatic PR from RestAPI-PR1079 Azure/azure-sdk-for-ruby#738

Closed

mccleanp pushed a commit that referenced this pull request Mar 23, 2022

New Falcon Resource Provider APIs (#1079)

1466a70

* New Falcon Resource Provider APIs * Address GO SDK failure * Remove unused example file * Addressed PR comments * Addressed PR comment about long-running-operation

Conversation

btasdoven commented Mar 29, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR information

Quality of Swagger

Uh oh!

msftclas commented Mar 29, 2017

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!

dsgouda commented Mar 29, 2017

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!

dsgouda commented Mar 30, 2017

Uh oh!

dsgouda commented Mar 30, 2017

Uh oh!

AutorestCI commented Mar 30, 2017

Uh oh!

AutorestCI commented Mar 30, 2017

Uh oh!

AutorestCI commented Mar 30, 2017

Uh oh!

Reviewers

Assignees

Labels

Projects

btasdoven commented Mar 29, 2017 •

edited

Loading