-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NIFIREG-395 - Implemented the ability to import and export versioned … #5107
Conversation
…flows through the UI. - Added REST endpoints in BucketFlowResource for importVersionedFlow and exportVersionedFlow. - Added import and export dialogs. - Set the initial value for the Bucket dropdown menu in the Import dialogs. - Added frontend and backend integration tests. - Created ExportedVersionedFlowSnapshot object. - Added test resource file and updated rat configuration to skip the file during contrib-check. - Refactored frontend and server side code. - Updated Flow Actions menu hover and focus styles.
@exceptionfactory @bbende @sardell @andrewmlim Would you review one more time? Opened a new PR after NiFi Registry was migrated into NiFi. There are no code changes on my end since your last reviews/approvals. Thanks! |
+1 LGTM Ran through same test cases I did for apache/nifi-registry#319 including some basic authorization testing. |
Taking another look now... |
+1 (non-binding). LGTM! |
+1 everything still looks good, nice work! One minor thing I noticed while doing another test... in the first import, there is no box to specify Comments for the first version, but there is Flow Description which is technically a different field for the overall versioned flow, then on future imports of additional versions there is a Comments field. I'm in no way saying to hold this up, just wanted to note it for future consideration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks @mtien-apache!
@bbende Do you propose adding a Comments box in the dialog for 'Import New Flow' (first version)? I can create a separate JIRA for this. Thanks. |
Yes I think it makes sense to allow it. It would be consistent with Start Version Control from NiFi which has a Description and Comments field for the first version. |
Here is the JIRA (NIFI-8660) to allow adding Comments when importing a new flow. |
I see 4 +1's but no objections. Based on that, will merge. |
…flows through the UI. (apache#5107) - Added REST endpoints in BucketFlowResource for importVersionedFlow and exportVersionedFlow. - Added import and export dialogs. - Set the initial value for the Bucket dropdown menu in the Import dialogs. - Added frontend and backend integration tests. - Created ExportedVersionedFlowSnapshot object. - Added test resource file and updated rat configuration to skip the file during contrib-check. - Refactored frontend and server side code. - Updated Flow Actions menu hover and focus styles.
…flows through the UI. (apache#5107) - Added REST endpoints in BucketFlowResource for importVersionedFlow and exportVersionedFlow. - Added import and export dialogs. - Set the initial value for the Bucket dropdown menu in the Import dialogs. - Added frontend and backend integration tests. - Created ExportedVersionedFlowSnapshot object. - Added test resource file and updated rat configuration to skip the file during contrib-check. - Refactored frontend and server side code. - Updated Flow Actions menu hover and focus styles.
…flows through the UI. (apache#5107) - Added REST endpoints in BucketFlowResource for importVersionedFlow and exportVersionedFlow. - Added import and export dialogs. - Set the initial value for the Bucket dropdown menu in the Import dialogs. - Added frontend and backend integration tests. - Created ExportedVersionedFlowSnapshot object. - Added test resource file and updated rat configuration to skip the file during contrib-check. - Refactored frontend and server side code. - Updated Flow Actions menu hover and focus styles.
…flows through the UI.
Added REST endpoints in BucketFlowResource for importVersionedFlow and exportVersionedFlow.
Added import and export dialogs.
Set the initial value for the Bucket dropdown menu in the Import dialogs.
Added frontend and backend integration tests.
Created ExportedVersionedFlowSnapshot object.
Added test resource file and updated rat configuration to skip the file during contrib-check.
Refactored frontend and server side code.
Updated Flow Actions menu hover and focus styles.
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically
main
)?Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not
squash
or use--force
when pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean install
at the rootnifi
folder?LICENSE
file, including the mainLICENSE
file undernifi-assembly
?NOTICE
file, including the mainNOTICE
file found undernifi-assembly
?.displayName
in addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.