This repository has been archived by the owner on Jul 22, 2021. It is now read-only.
NIFIREG-242 Two-way synchronization of git repository backed flows #166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
make the testLoadNonExistingDir- Test pass.
getLatestChangesOfRemoteRepository
synchronization.
added 5 commits
April 1, 2019 14:31
…ibility with posix permissions
if not specified otherwise
DennisSeiffert
changed the title
|
Hi, I am trying 2 way synchronization and it is not working for me. I made some changes to the local repo and just modifying the yaml file & json file [ for testing ] and it didn't reflect in the the registry GUI .. even after restarting. Do i need to do anything after that ? |
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request solves NiFi registry ticket with the number #NIFIREG-242 .
The pull request introduces code changes concerning the gitflowpersistenceprovider and extends its behaviour by submitting new features like 'reset git repository', 'get latest changes' and a 'get status' functionality. The work is based on #NIFIREG-209 and uses the the metadata synchronization.
By capturing the new features in a new synchronization context (interface ProviderSynchronization), it may be possible to integrate other providers into the same concept of synchronization.
We did not squash the entire history because from our point of view it might be easier to review. Please let us know, if you prefer it otherwise.
We are already using this feature in a k8s production environment.
Cheers