Context

Currently, events produced by the GCS source are all typed as com.google.cloud.storage.notification. This is limiting particularly if you plan to listen to different types of GCS notifications (OBJECT_FINALIZE, OBJECT_METADATA_UPDATE, OBJECT_DELETE, OBJECT_ARCHIVE) but plan to route different notifications to different destinations.

Comparatively, the AWSS3 source and the Azure Blob Storage source already produce distinct event types for each type of change on an storage bucket.

Requirements

The GCS source should produce a distinct event type per type of bucket notification. Below is a suggestion for the names of these event types:

com.google.cloud.storage.objectfinalize
com.google.cloud.storage.objectmetadataupdate
com.google.cloud.storage.objectdelete
com.google.cloud.storage.objectarchive

Alternatively we could also keep the punctuation closer to the original name of the event, such as:

com.google.cloud.storage.OBJECT_FINALIZE