...
- TO check with client that anyone using this schema. If yes, We need to deprecate this version and create the new version.
- To keep schema consistent map all the properties of 'DMIAsynRequestResponse' to 'NCMPAsynRequestResponse → Event' instead of 'NCMPAsynRequestResponse → ForwardedEvent'.
- For now 'response-data' of 'DMIAsynRequestResponse' is mapping to 'additional-properties' of 'forwardedEvent' in 'NCMPAsynRequestResponse' .
- 'response-date → payload' should be matched to the 'forwardedEvent → forwardedEventData →forwardedEventPayload ' .
- If the above mapping is wrong, We need to update the mapping to the appropriate one.
- If we agreed with team to use 'Event' instead of ' forwardedEvent', We need to introduce the 'schemaVersion' property in 'Event' schema
- If the above point is agreed, We need to keep only the payload inside the 'Event'.
...
Conclusion
- The schema consists of duplicated data.
- Instead of using the type 'Event' we used the new type 'ForwardedEvent'.
- CPS 'additionalProperties (privateProperties)' field is clashed with the framework generated 'additionalProperties' field.
- Proposed the new schema at CPS Events Structure for the agreement.
- Once the above one agreed, We work the same at
Jira server ONAP Jira serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CPS-1660 - Identified 'response-data' was miss-mapped to ForwardedEvent → (additionalProperties ( generated by the framework)).
...