[
https://issues.apache.org/jira/browse/NIFIREG-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977449#comment-16977449
]
Rabi Kumar K C commented on NIFIREG-227:
----------------------------------------
Hi [~kdoran], I was following
[https://community.cloudera.com/t5/Community-Articles/Storing-Apache-NiFi-Versioned-Flows-in-a-Git-Repository/ta-p/248713]
tutorial for gitflowpersistenceprovider so build the current master branch and
used the tar in nifi-registry-assembly. While trying to save the flow I got an
exception saying that versioned flow identifier cannot be specified when
creating a new flow which means that versioned flow identifier was already set
before calling StandardServiceFacade.validateCreationOfRevisableEntity from
StandardServiceFacade.createflow which throws an exception if
entity.getIdentifer is not null. So added some log messages in
BucketFlowResource.createflow and StandardServiceFacade.createflow to check if
versioned flow identifier was actually set for which I have attached the logs
above. And this behavior is occurring without making any changes in master
branch.
Please do let me know if above is a desired behavior.
> GitFlowPersistenceProvider option to clone repo on startup
> ----------------------------------------------------------
>
> Key: NIFIREG-227
> URL: https://issues.apache.org/jira/browse/NIFIREG-227
> Project: NiFi Registry
> Issue Type: New Feature
> Reporter: Kevin Doran
> Assignee: Rabi Kumar K C
> Priority: Minor
> Attachments: nifi-registry-app.log
>
>
> To build on NIFIREG-209, which added the ability to rebuild the flow metadata
> database from a git repository if the metadata is empty on startup, it would
> also be nice to have the option to clone a git repo on startup if there is
> not a local git repo and a remote is configured.
> The proposed feature is for the GitFlowPersistenceProvider, to check if there
> is a local repository during startup. If the repository is not present, and a
> remote is configured (to push to), start by cloning the remote.
> The use case is *not* supporting multiple registry instances syncing to the
> same git repository (that would require more work). Rather, the use case is
> recovery from a remote git repository. This will be especially useful when
> launching new docker containers as it would give the ability to create a
> container initialized from a remote git repo just via configuration options
> and not an explicit git clone step in the image/container.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
