[NIFI-13724] NiFi Registry Events Include Additional Metadata

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.0.0, 1.29.0
• Component/s: NiFi Registry
• Assignee: Dye357
• Reporter: Dye357
• Created: 06/Sep/24 18:27
• Updated: 26/Oct/24 16:42
• Resolved: 21/Oct/24 16:06

Description

Currently the Nifi Registry EventFactory adds a few pieces of metadata to the EventType - when writing a custom extension for Nifi Registry a developer is limited in the amount of information they have about the event – this ticket would expand the scope of metadata included in each event to include the Name, Description and Timestamps. 

As a work-around we were using the nifi-registry-client to use the provided IDs to enrich our dataset however we've run into problems:

1. The nifi registry client is broken when running inside an Nifi Registry extension due to JavaX/Jakarta classpath issues. (Separate ticket)

2. This the most important of the two points – if we have a Bucket Deleted or Flow Deleted event only having the ID is useless because we can no longer query the API to get the name and description for the Entity in question which has led to some auditing/accountability concerns. 

I'm putting together a PR to include the additional specified metadata in the EventFactory. The PR should be merge-able on 1.x and 2.x

Issue Links

• links to: GitHub Pull Request #9239
• links to: GitHub Pull Request #9433