[Communication] Remove async response from RegenerateKey (Azure#13426)

MirzaSikander · Mar 22, 2021 · 1c65b60 · 1c65b60
1 parent b612e7d
commit 1c65b60
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 9 deletions.
diff --git a/...tion/resource-manager/Microsoft.Communication/stable/2020-08-20/CommunicationService.json b/...tion/resource-manager/Microsoft.Communication/stable/2020-08-20/CommunicationService.json
@@ -617,12 +617,6 @@
               "$ref": "#/definitions/CommunicationServiceKeys"
             }
           },
-          "201": {
-            "description": "Created and an async operation is executing in background to make the new key take effect. The response contains new keys and an Azure-AsyncOperation header to query the async operation result.",
-            "schema": {
-              "$ref": "#/definitions/CommunicationServiceKeys"
-            }
-          },
           "default": {
             "description": "Error response describing why the operation failed.",
             "schema": {

diff --git a/...on/resource-manager/Microsoft.Communication/stable/2020-08-20/examples/regenerateKey.json b/...on/resource-manager/Microsoft.Communication/stable/2020-08-20/examples/regenerateKey.json
@@ -14,9 +14,6 @@
         "primaryKey": "1234",
         "primaryConnectionString": "endpoint=http://example.com;accesskey=1234"
       }
-    },
-    "201": {
-      "body": {}
     }
   }
 }