See #4 in https://wiki.onap.org/display/DW/CPS-391Spike%3A+Define+and+Agree+NCMP+REST+Interface#CPS391Spike:DefineandAgreeNCMPRESTInterface-Datastore,PathsandFormatCombinationsforWriteOperations

for Patch operations the media-type/content-type is import to distinguish between 'plain' (merge) path operations and yang-path operations.

See also https://datatracker.ietf.org/doc/html/rfc8072 and https://www.tail-f.com/yang-patch-and-restconf/

The current code does store the 'original' contentType as 'dataType' towards DMI Plugin' for this user story it is important that this is verified/demoed

https://wiki.onap.org/display/DW/CPS-577%3A+Prepare+the+request+from+client+and+send+write+request+to+dmi-plugin

in DMI Plugin API it should just be another operation enum-value

Response code from SDNC Patches? maybe start here: https://wiki.onap.org/display/DW/CPS-395+Spike%3A+SDNC+Interface+for+CRUD+and+Patch+Operations

Update https://wiki.onap.org/display/DW/CPS-577%3A+Prepare+the+request+from+client+and+send+write+request+to+dmi-plugin with details on response type and status code

A/C

1. Good en clear OpenAPI definitions including examples
2. Updated Wiki with response details shared and agreed with team
3. E2E test using CSIT (incl. demo to team when both side are done)
   1. Not sure what is supported by SDN-C, this might affect demo!
   2. if need just show generated request towards SDNC-C and show the original content-type.
4. Update Release notes with OpenApi

Out of scope

• E2E demo of both patch operations is nice to have if easy to realize with SDNC