Hi Kalpana
I can give you a simple use case for providing details of a deleted entity - suppose that you have some archival mechanism that stores old objects in secondary storage. You would want this mechanism to take the entity as it is deleted so that it can be stored there.
And since the entity has already been deleted from primary storage, the only details available are in the entity delete event.
There may be additional use cases.
So I would suggest that you consult with your potential event consumers before deciding how to populate the entity delete event.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Oct 30, 2020 02:21
From: Kalpana HV
Subject: Resource deletion notification
Hi All,
As per design guidelines, the notification payloads is
{"eventId": "eventId",
"eventTime": "event Time",
"eventType": "event Type",
"event": {
"resource": "--RESOURCE SAMPLE --"
}
}
Its reasonable to provide resource's content in "event" object when the resource is created or updated. Is it required to provide deleted objects fields in the remove notifications.
Thanks,
------------------------------
Kalpana HV
Colt Technology Services
------------------------------