NIFI-13138 - Add extensions name and description in NiFi Registry

[pvillard31]

Summary

NIFI-13138 - Add extensions name and description in NiFi Registry

Tracking

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

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

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

Pull Request Formatting

• Pull Request based on current revision of the main branch
• 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

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

UI Contributions

• NiFi is modernizing its UI. Any contributions that update the current UI also need to be implemented in the new UI.

Licensing

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

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks for this improvement to the Registry extension details @pvillard31. The general approach looks straightforward. The only potential concern is that the sections for Processors, Controller Services, and Reporting Tasks will be empty depending on what is contained in the given bundle. It seems like it would be better to list only those sections that apply to the given bundle. Another alternative could be to have the number of components listed next to the section, such as Processors: 0, which would support showing the sections in all cases, but more clearly indicating the presence of absence of items for that section.

[pvillard31]

Thanks @exceptionfactory - added the number of components per type

[pvillard31]

@exceptionfactory - I will update this PR to also include Parameter Providers and Flow Analysis Rules. Is there something else you'd expect to see here?

[exceptionfactory]

@exceptionfactory - I will update this PR to also include Parameter Providers and Flow Analysis Rules. Is there something else you'd expect to see here?

Thanks @pvillard31, I was planning on circling back to this, so if you can add those items, I think it should be ready to merge.

[pvillard31]

Done, thanks @exceptionfactory