GET responses following a successful DELETE should be returning 404. … (

#13054) * GET responses following a successful DELETE should be returning 404. Only the DELETE response is to return 204 if the resource didn't exist (it allows idempotent deletes). (cherry picked from commit b752a19) * Removing 404 as it is taken care by default response.
Azure · Feb 23, 2021 · 4913df4 · 4913df4
1 parent ab9e37d
commit 4913df4
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 6 deletions.
diff --git a/...KeyVault/preview/2021-04-01-preview/examples/ManagedHsm_getPrivateEndpointConnection.json b/...KeyVault/preview/2021-04-01-preview/examples/ManagedHsm_getPrivateEndpointConnection.json
@@ -25,9 +25,6 @@
           }
         }
       }
-    },
-    "204": {
-      "headers": {}
     }
   }
 }
diff --git a/...n/keyvault/resource-manager/Microsoft.KeyVault/preview/2021-04-01-preview/managedHsm.json b/...n/keyvault/resource-manager/Microsoft.KeyVault/preview/2021-04-01-preview/managedHsm.json
@@ -392,9 +392,6 @@
               "$ref": "#/definitions/MHSMPrivateEndpointConnection"
             }
           },
-          "204": {
-            "description": "The private endpoint connection does not exist."
-          },
           "default": {
             "description": "The error response describing why the operation failed.",
             "schema": {