...
Proposed outcome (Schema 5)
Code Block | ||
---|---|---|
| ||
{ "version": "1.0", “eventId” : “dse345r-df43”, “eventCorrelationId” : <the-subscription-id-issued-for-original-client-subscription-request>, "eventType": "subscriptionCreatedOutcomesubscriptionResponse", # or subscriptionCreatedPartialOutcome“eventTime” "event": {<time>, "subscriptiondata": { "clientID": "SCO-9989752", "name": "cm-subscription-001" }, "predicates": { “rejectedTargets” : “statusCode” : 201, # Some error code reflecting partial success. ** “statusMessage” : “Partially Applied Subscription”, “additionalInfo” : { “fail” : { “details” : “faulty subscription format for target(s)”, “targets” : [“cmhandle1”, “cmhandle2”, “cmhandle3”] }, “acceptedTargets” : [“cmhandle1”, “cmhandle2”, “cmhandle3”], “pendingTargets” : “pending” : { “details” : “EMS/node connectivity issues, retrying”, “targets” : [“cmhandle4”, “cmhandle5”, “cmhandle6”], } } } } } ** 202 could indicate complete failure – "data": { “statusCode” : 202, # Some error code reflecting complete rejection of the request “statusMessage” : “Subscription rejected : Faulty Subscription Data”, “additionalInfo” : { “fail” : { “details” : “//NRxxCellDU is not a valid subscription type” }, |
Open Question: what headers do we need?
...