A/C
See details on page https://wiki.onap.org/display/DW/CPS-391Spike%3A+Define+and+Agree+NCMP+REST+Interface
See examples on https://wiki.onap.org/display/DW/CPS-455+Spike%3A+support+options+for+%27fields%27+and+%27depth%27+parameters

This is to support combination #6 in the 'Datastore, Paths and Format Combinations for Read Operations' table
In DMI PLugin we need to do a transformation of the URL

Url -

{dmiroot}

/dmi/v1/ch/<cmHandle>/data/ds/ncmp-datastore:passthrough-operational/

{resourceIdentifier}

?fields=

{fields-expression}

example of uri with fields: {sdncroot}/rests/data/network-topology:network-topology/topology={topologyId}/node={cmHandle}/yang-ext:mount/resourceIdentifier?fields={fields-expression}

?content=all

example of uri with depth:

{sdncroot}

/rests/data/network-topology:network-topology/topology=

{topologyId}

/node=

{cmHandle}

/yang-ext:mount/resourceIdentifier?depth=

{depth-expression}

?content=all

topologyId is a configuration param
resourceIdentifier is the module name
We will expect specific fields in the uri
expected format : application/yang-data+json
expected resource-path: Restconf compatible

Supported parameters (depending SND-C/ODL interface) 

• fields (as incoming fields value)
• depth (as incoming fields value)
• config (all - determined by ds param)

Basic error handling

Output format - test with json and yang-data + json (get value from incoming accept header and use for outgoing accept header)

Out of Scope

• Demo using different parameters (demo when NCMP part is done instead)
• No validation