Overview

CPS-1065 Spike: CM data notifications from NCMP to applications including subscriptions - Developer Wiki - Confluence (onap.org)

1. We will receive the events in cm-avc-subscription topic.
   [refer : org/onap/cps/ncmp/api/impl/async/NcmpAsyncRequestResponseEventConsumer.java]
2. Create the Subscription event schema in format  and convert the message to Java Object ( CPS-1065 Spike: CM data notifications from NCMP to applications including subscriptions - Developer Wiki - Confluence (onap.org) )
3. Consume the SubscriptionCreated event and print the object in the logs.
4. We should only consume the messages which have dataCategory as CM and silently ignore others.
5. Groovy tests to produce SubscriptionCreated event using testcontainers.
   [refer : org/onap/cps/ncmp/api/impl/async/CpsAsyncRequestResponseEventIntegrationSpec.groovy ]
6. Demo using some Kafka Producer UI/cmd tool.
7. If we fail to covert the incoming message to the required format we just log it on the console.

A/C

1.  ** Create Proposal page , agree with the team and stakeholders.
2.  The topic should be configurable. defaults to cm-avc-subscription
   Property name : app.ncmp.avc.subscription-topic{}
3. Demo that the message is consumed and logged and it is in the agreed format.
4. Demo that non CM dataCategory events are ignored.

Open Questions

1. Are we gonna document it in our open source documentations. ( Should be document the functionality ,  just the configurable params or both ) 

Out of Scope

1. Not persisting anything , next user story will take care CPS-1394