GitHub user mcgilman opened a pull request:
https://github.com/apache/nifi/pull/2219
NiFi-4436: Add UI controls for starting/stopping/reverting flow versioning
@markap14 Please review the frontend/backend integration of the early
version control capabilities utilizing the local file-based registry test
client. Should be able to start/stop/revert version control on a per process
group basis using the context menu items.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mcgilman/nifi NIFI-4436
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2219.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2219
----
commit b0cf561c9977924dab9df656bc7dd795820e0b8c
Author: Mark Payne <[email protected]>
Date: 2017-08-10T14:02:35Z
NIFI-4436:
- Initial checkpoint: able ot start version control and detect changes, in
standalone mode, still 'crude' implementation
- Checkpoint: Can place flow under version control and can determine if
modified
- Checkpoint: Change version working in some cases. Does not work if
processor removed because COMPONENT_REMOVED type has ComponentA whose ID is the
VersionedComponentID but we are trying to call ProcessorDAO.get() with this ID
- Checkpoint: Able to change flow from Version 1 to Version 2 and back. Not
yet tested with controller services. Have not tried changing/removing
connections. Not cluster-friendly yet. All inline, not in background. Have not
taken into account ports, funnels, remote ports, etc. Have not tested with
Labels yet
- Checkpoint after implementing ClusterReplicationComponentLifecycle
instead of JerseyClientComponentLifecycle
- Checkpoint: Updated to allow starting version control and updating
version in clustered mode
- Checkpoint: Updated versioning endpoint so that when version of a flow is
updated, the bundle information is populated and the snapshot is replicated to
the cluster.
- Checkpoint: Implemented endpoint for reverting to previously sync'ed
version of a flow and updated version control endpoint so that Process Group
can be pushed as a new version to existing flow instead of only creating a new
flow
- Checkpoint: Updated so that if a Process Group is under Version Control
and it has a child Process Group, which is also under Version Control, we can
handle that gracefully. Not yet tested because it depends on updates to the
nifi-registry module, which can't be compiled due to maven dependency conflicts
commit b0ea3397862375244d37b939f396d320355a1ebc
Author: Matt Gilman <[email protected]>
Date: 2017-10-12T16:29:05Z
NIFI-4436:
- Adding support to save a version of a flow based on a selected Process
Group.
- Adding support for revert changes back to the most recent version.
- Adding support to disconnect from version control.
----
---
