...
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Open Issues & Decisions
Description | Notes | Decision | |
|---|---|---|---|
| 1 | Priority of async calls | In Istanbul, async calls are required only in pass-through cases. NCMP does not have to handle these requests | |
| 2 | Will we use the data node wrapper on GET rest operations? | Currently, we wrap the response of GET operations using the data node wrapper. | |
| 3 | In the URI will we distinguish between data and operations (RFC calls) as part of the path? | e.g. http://localhost:8080/cps/api/v1/data http://localhost:8080/cps/api/v1/operation | |
| 4 | Parent data resource identifier can handle any path using the same query parameter
| ||
| 5 | Yml should include return types and examples of the payload | ||
| 6 | camel case or dash in URI | we will use a dash for param names e.g. cm-handle | |
| 7 | Insert /resource-path in front of the resource path to prevent ambiguous paths | <OP>/ncmp /<v{v-number}>/cmhandle/<cm-handle>/<data|operations|{ncmp-action}>/ds/{datastore}/resource-path/<resource-path>?<query> | |
| 8 | Granularity of update scenarios (and priority) |
| |
| 9 | There is no automatic fallback option for datastore | The client will have the specify the datastore | |
| 10 | fields is a rest conf option, investigate is it fully supported by onap | ||
| 11 | Agree on URI syntax | Proposed syntax by CPS team <OP>/ncmp /api/<v{v-number}>/ch/<cm-handle>/<data|operations|{ncmp-operation}>/ds/{datastore}/[rs]{resource-path}?{query} |
RESTCONF/NETCONF relationship
...