NIFI-13724 Add additional metadata to Registry events

[Dye357]

Summary

NIFI-13724

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• [ X] Apache NiFi Jira issue created

Pull Request Tracking

• [ X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• [ X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• [X ] Pull Request based on current revision of the main branch
• [X ] Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• [ X] Build completed using mvn clean install -P contrib-check
  • [ X] JDK 21

Licensing

• [ n/a] New dependencies are compatible with the Apache License 2.0 according to the License Policy
• [ n/a] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• [ X] Documentation formatting appears as expected in rendered files

[Dye357]

Does anyone have some time to review the PR I submitted?

[bbende]

General idea seems good, just a few comments about handling optional fields, and a question about whether FLOW_VERSION is really needed to be added.

[Dye357]

Just pushed a new commit to fix a whitespace issue.

[bbende]

Latest updates look good, thanks for following up with the changes

[Dye357]

Thanks @bbende! What would I need to do to have this PR also dropped onto the 1.x support branch. Ideally for the 1.28 release?

[bbende]

@Dye357 At this point it mostly requires two separate PRs, one to main and then one to support/nifi-1.x. For most NiFi specific changes, the cherry pick doesn't apply cleanly because everything has changed, but since this only registry, hopefully you can just create a local branch from support/nifi-1.x, cherry pick the commit, push the branch to your fork and create another PR against support/nifi-1.x.