NIFI-14319: Create initial project structure for new NiFi Registry UI

[sardell]

Summary

NIFI-14319

Description

This PR establishes the initial project setup for the new NiFi Registry UI and includes the new explorer view.

Testing

Build and start the old registry project with maven using the existing instructions. Next, run npm ci at nifi-frontend/src/main/frontend and start the app by running npx nx run nifi-registry:serve. Visit http://localhost:4204/nifi-registry/ to see the new explorer page. Compare the old explorer view with the new one, ensuring feature parity between the two views. Run unit tests with npx nx run nifi-registry:test.

NOTE: buckets cannot be created through the new UI yet, so in order to test the functionality of the new explorer view you must first create a bucket through the old UI.

Considerations

Styling - The old logo was created with a much darker background color in mind. It may be time for a refreshed logo, but for now I simply added the old one to the header along with a heading containing the application's name.

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

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 work on NiFi Registry @sardell!

The standard ci-workflow builds are failing, does this build locally for you, or is this still a work in progress that should be marked as draft?

[sardell]

@exceptionfactory Thanks for raising the failing CI to my attention. It looks like the failure was due to the favicon missing from the old registry ui directory. I accidentally deleted it when copying over images to the new project. I noticed the missing file while working on this PR and added the file back, but it seems that file was accidentally added to the .gitignore (I think intention of that .gitignore line was to ignore the generated favicon, not all instances of that file). I believe this is why I could successfully build locally and also see the CI failures you pointed out.

Fingers crossed the CI passes this time. I'll keep an eye on it.

UPDATE: Looks like the CI build is now failing on a build step that runs fine locally. Will need to investigate a little further.

[exceptionfactory]

Thanks for the update @sardell, although the build completes on macOS, it is failing on Linux and Windows.

On Linux, there appears to be something platform-dependent:

[INFO] ::group::❌ > nx run shared:build:production
[INFO] 
[INFO] Building Angular Package
[INFO] 
[INFO] ------------------------------------------------------------------------------
[INFO] Building entry point '@nifi/shared'
[INFO] ------------------------------------------------------------------------------
[INFO] - Compiling with Angular sources in Ivy full compilation mode.
[INFO] ✖ Compiling with Angular sources in Ivy full compilation mode.
[INFO] 
[INFO]  NX   The package "@esbuild/linux-x64" could not be found, and is needed by esbuild.

[elcsiga]

looks good for the 1st glance, I post my first comments, will continue the review soon

[scottyaslan]

@sardell thanks for the PR! I have left several comments on things that need to be addressed. Apologies that there are so many comments as I know this is a big undertaking and your effort here is appreciated. I am sure I will have more comments after you make the requested changes.

Also, I didn't have a great place to leave the following comments so placing them here:

Please run prettier and lint:fix. There are several strange formatting issues.

Please delete nifi-registry/public directory and the favicon.ico.

[sardell]

@scottyaslan @elcsiga Thank you both for taking the time to review this PR! I've addressed all your comments. When you have a chance, could you please take another look?

@scottyaslan I've updated the Jira tickets for the Registry UI work to be tasks organized under an epic per your suggestion. I've also started breaking down the work into much smaller chunks (see the ticket for the buckets view and its subtasks for an example). I'll continue this work for the users and groups view.

[sardell]

@scottyaslan @elcsiga Could you please re-review when you have time?

[scottyaslan]

Reviewing...

[scottyaslan]

Hey @sardell! I have reviewed this PR and it is looking good. There are still several things to get dialed in but all in all this is headed in the right direction. Please let me know if you have any questions or comments or if you need any clarity on my latest set of comments.

[scottyaslan]

@sardell also please run npx nx run prettier:fix.

[scottyaslan]

@sardell I hope to get back to reviewing this next week. Sorry for the delay!

[scottyaslan]

@sardell sorry for the delay in getting back to this. Thanks for the updates! I think we are close. Please rebase and I left just a few more comments. Mostly, I would like to see the route be renamed back to 'explorer' and get rid of the queryParams.

[sardell]

@scottyaslan Your latest round of feedback has been addressed. Please take another look whenever you have time. Thanks!

[scottyaslan]

Thanks @sardell this is a great start!