feat(nifi): Restore flows directly from JSON file instead of using versioning #194
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
dervoeti
force-pushed
the
feat/nifi-drop-flow-versioning
branch
from
9419581 to
dbae86d
Compare
dervoeti
force-pushed
the
feat/nifi-drop-flow-versioning
branch
from
dbae86d to
2ac3a07
Compare
dervoeti
changed the title
dervoeti
moved this from Development: Waiting for Review
to Development: Done
in Stackable Engineering
dervoeti
added a commit
that referenced
this pull request
Mar 26, 2025
…rsioning (#194) feat: remove versioning from flow restore process
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
While the demos are currently working, NiFi 2 reports a status drift to the versioned components when comparing the deployed state with the state in Git. This is wrong, but we can't really work around it and it might irritate users.
Also, we saw some problems related to Github's rate limits when installing NiFi demos too often on the same machine.
This PR drops the whole process of versioning, since it is not needed for the demos. It was just our first approach as a replacement for the "templates" functionality that was removed with NiFi 2. Instead of using versioning, we now download the JSON files from Github via HTTP and then directly create the Flows via NiFis
/process-groups/uploadAPI.