diff options
| author |   Igor D.C <igor.duarte.cardoso@intel.com> | 2020-07-26 05:30:08 +0000 |
|---|---|---|
| committer | Igor D.C <igor.duarte.cardoso@intel.com> | 2020-07-26 05:32:30 +0000 |
| commit | 6186da3b2a7c30b4979c9b8530ca59667ae12446 (patch) | |
| tree | 7d17ffbb00e1977f043da73c12d4cb7e5c223116 | |
| parent | 39b7d2f8a79f23141301e7b9abf7bf3a0f2e8f21 (diff) | |
Correct add-cluster metadata form field syntax
Currently, the "metadata" form field expects JSON with the
top-level dictionary "metadata", and then the actual data inside.
The Postman collection doesn't provide that top-level dict which
results in a failed API call when using the Postman request as is.
Issue-ID: MULTICLOUD-1143
Signed-off-by: Igor D.C <igor.duarte.cardoso@intel.com>
Change-Id: I5f0c4b699eb38f7e133e9d3d55eb2a0eda890601
| -rw-r--r-- | docs/EMCO.postman_collection.json | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/EMCO.postman_collection.json b/docs/EMCO.postman_collection.json index 0dad51e0..aebd0ebd 100644 --- a/docs/EMCO.postman_collection.json +++ b/docs/EMCO.postman_collection.json @@ -14834,7 +14834,7 @@ "formdata": [ { "key": "metadata", - "value": "{\"name\":\"<string>\",\"description\":\"<string>\",\"userData1\":\"<string>\",\"userData2\":\"<string>\"}", + "value": "{\"metadata\":{\"name\":\"<string>\",\"description\":\"<string>\",\"userData1\":\"<string>\",\"userData2\":\"<string>\"}}", "type": "text" }, { @@ -15745,4 +15745,4 @@ } ], "protocolProfileBehavior": {} -}
\ No newline at end of file +} |