Filter out requests by action

For every new component that is deployed in our maven repository, two requests will be sent. The main difference between these two requests is the action field found in the payload.

It first sends this payload informing that a new component has been created:

{
 "timestamp":"2018-08-09T16:16:27.046+0000",
  ...
  "action":"CREATED",
  "component":
   {
    "id":"4b378653591c67228e5a087b6a06f6fb",
    "name":"openbis-tester-cli",
    "group":"life.qbic",
    "version":"2.0.1"
    }
}

And then it sends word that the component has been updated.

{
 "timestamp":"2018-08-09T16:16:27.313+0000",
  ... 
  "action":"UPDATED",
  "component": 
    {
     "id":"4b378653591c67228e5a087b6a06f6fb",
     "name":"openbis-tester-cli",
     "group":"life.qbic",
     "version":"2.0.1"
    }
}

Furthermore, there's a different action that could potentially break this service. If action is set to DELETED, this service would attempt to download an asset that is no longer there.

This service should only process actions of type UPDATED.

qbicsoftware-archive / nexus-listener-service

Filter out requests by action #1