...
| draw.io Diagram | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
| Jira | ||||||||||||||||||||
| server | ONAP Jira | |||||||||||||||||||
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution | |||||||||||||||||||
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | |||||||||||||||||||
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | CPS-577||||||||||||||||||
|
- Since the DMI Plugin always needs an request body for at least the 'Additional Parameters' CPS_NCMP wil have to use PUT or POST to make a any (read or) write request.
- The DMU Plugin will coded to support both POST and PUT for backward compatibility (TBC maybe not necessary, since CPS_NCMP is only client of DMI-Plugin)
- The actual operation will be determine with 'operation' field in body. If this is not supplied 'read' wil be assumed as the default operation irrespective of the HTTP method used