Open APIs

Expand all | Collapse all

Resource deletion notification

  • 1.  Resource deletion notification

    TM Forum Member
    Posted Oct 30, 2020 02:22
    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
    ------------------------------


  • 2.  RE: Resource deletion notification

    TM Forum Member
    Posted Nov 01, 2020 01:22
    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.
    ------------------------------



  • 3.  RE: Resource deletion notification

    TM Forum Member
    Posted 30 days ago
    Edited by Kalpana HV 30 days ago
    Thank you @Jonathan Goldberg. It helps. Suppose, event consumer is not interested in content of deleted entity,  can we have notification payload without event attribute or should we create an API with TMF mandated fields and another  API with customer specific fields. Seems the new Event API is addressing this problem as it bothers only notification publication messages and not on consumption of notification messages?

    Best Regards​

    ------------------------------
    Kalpana HV
    Colt Technology Services
    ------------------------------



  • 4.  RE: Resource deletion notification

    TM Forum Member
    Posted 29 days ago
    Hi Kalpana

    As far as I am aware, the event notification pattern does not create different events for different consumers. It's not scalable, you will end up having to tailor events each time a new fussy consumer appears. Similarly, why would you go to the effort to create a new API?

    The whole point of the events is to "tell the world" what happened - it's up to event consumers to decide what information they need and use it. What they don't need they can ignore.

    ------------------------------
    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.
    ------------------------------



  • 5.  RE: Resource deletion notification

    TM Forum Member
    Posted 29 days ago
    Agreed @Jonathan Goldberg. Thank you.

    Best Regards​​

    ------------------------------
    Kalpana HV
    Colt Technology Services
    ------------------------------