[Quantum] Fixing correctness issue regarding the CheckNameAvailability (

Azure#13360) * [Quantum] Fixing correctness issue regarding the CheckNameAvailability API * Adding read-only property
MirzaSikander · Mar 22, 2021 · 88b71df · 88b71df
1 parent b7b0460
commit 88b71df
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/...t.Quantum/preview/2019-11-04-preview/examples/quantumWorkspacesCheckNameAvailability.json b/...t.Quantum/preview/2019-11-04-preview/examples/quantumWorkspacesCheckNameAvailability.json
@@ -11,8 +11,9 @@
   "responses": {
     "200": {
       "body": {
-        "nameAvailable": true,
-        "reason": ""
+        "nameAvailable": false,
+        "reason": "AlreadyExists",
+        "message": "Resource name already exists"
       }
     }
   }

diff --git a/...cation/quantum/resource-manager/Microsoft.Quantum/preview/2019-11-04-preview/quantum.json b/...cation/quantum/resource-manager/Microsoft.Quantum/preview/2019-11-04-preview/quantum.json
@@ -930,6 +930,11 @@
         "reason": {
           "type": "string",
           "description": "The reason of unavailability."
+        },
+        "message": {
+          "readOnly": true,
+          "type": "string",
+          "description": "The detailed info regarding the reason associated with the Namespace."
         }
       }
     }