- Get the latest study information from Kieran Mccarthy <kieran.a.mccarthy@ericsson.com>
- Create a Wiki page with a clear diagram showing NCM and DMI and its interfaces detailing the scope of THIS (and other) spike
- Update V1 of the interface (communicate with E2E Slicing)
- Detail CRUD operations
- Detail Patch
- Include datastore options (pass-through)
- Agree on parameter names and use them consistently
- Agree on JSON output format
- Resource 'path' can cover cps-paths, rest-conf path (for pass-through), and any proprietary paths
- Only 'hint' at
- async options
- bulk operations
A/C
- Wiki page detailing points above
- Share an agreement with the team
- Present at community
Out of scope
- actual YAML definitions (separate user story)
Open Issues & Decisions
Description | Notes | Decision | |
|---|---|---|---|
| 1 | Will we use the wrapper on GET rest operations? | Currently we wrap the response of GET operations using the data node wrapper. | |
| 2 | In the URI will we distinguish between data and operations as part of the path? | e.g. http://localhost:8080/cps/api/v1/data | |
| 3 | Parent data resource identifier can handle any path | ||
| 4 | Yml update with return types with examples of the payload |