...
Get all dataspaces
URL
Response body
Code Block {“dataspace-names”: [“data-space1”,” data-space2”,” data-space3”] }
Get single dataspace
URL
GET http://IP:PORT/cps/api/v1v2/admin/dataspaces/<dataspace-name>
Response body
Code Block { “dataspaceName”:”data-space1” }
Get all schema sets for a dataspaces
URL
GET http://IP:PORT/cps/api/v1v2/admin/dataspaces/<dataspace-name>/schema-sets
Response body (Reference get all dataspaces)
Code Block {“schemaSetNames”: [“schemaset-1”,” schemaset-1”,” schemaset-1”] }
...
- Create multiple root nodes in parallel (ref. Jira- CPS-341)
URL : POST http:// IP:PORT/cps/api/v1/dataspaces/<dataspace-name>/anchors/<anchor-name>/nodes?xpath=/
Existing request payload
New request payload (ref JSON file in CPS-341)
Code Block { "first-container": { "a-leaf": "a-value", "b-leaf": "b-value" } }
Code Block { "first-container": { "a-leaf": "a-value", "b-leaf": "b-value" }, "second-container": { "x-leaf": "x-value", "y-leaf": "y-value" }, "last-container": { "x-leaf": "x-value", "y-leaf": "y-value" } }
Note: For get multiple nodes we will use same API for get singular node to return. Can we have new end point for getting all root nodes ‘/nodes’.
- Create Dataspace should not have response body
URL : POST http://IP:PORT/cps/api/v1v2/dataspaces?dataspace-name=testDataspace
Current response body
testDataspace
Current response type
Text/plain
New response body
No response body
New response type
No response type
- Create schema-set should not have response body
URL : POST http://IP:PORT/cps/api/v1v2/dataspaces/<dataspace-name>/schema-sets
Current response body
schema-set1
Current response type
Text/plain
New response body
No response body
New response type
No response type
- Create an anchor should not have response body
URL : POST http://IP:PORT/cps/api/v1v2/dataspaces/<dataspace-name>/anchors?schema-set-name=<schema-set-name>&anchor-name=<anchor_name>
Current response body
anchor-test1
Current response type
Text/plain
New response body
No response body
New response type
No response type
- Create Node: if leaf list has only one leaf, then don’t force to use [] in request payload?
Current error message:
Only error code 500 Internal Server Error is returned.
The logs are as follows
Code Block org.springframework.web.util.NestedServletException: Request processing failed; nested exception is java.lang.IllegalArgumentException: Node (org:onap:ccsdk:sample?revision=2020-09-15)authors is not a simple type
here authors is name of leaf-list in schema/yang resource
Code Block leaf-list authors { type string; }
Sample error message:
Code Block Node (org:onap:ccsdk:sample?revision=2020-09-15)authors in schema is a leaf-list. Data received is of type list (or leaf).
Note: We need to handle above error and add a leaf list if there is only one leaf in leaf-list without forcing []. Include list as it accepts data without [], so do we need the error or change leaf-list to accept without []
...