[
https://issues.apache.org/jira/browse/NIFIREG-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975333#comment-16975333
]
Kevin Doran commented on NIFIREG-227:
-------------------------------------
[~rabikumar.kc] I've added you to the contributor role for the "NIFIREG"
project in Jira so you should be able to assign yourself issues now. Let me
know if you cannot and I'll look into it closer.
FWIW, anyone in the community is able to work on any issues and submit patches
/ PRs to the Apache repos. Assignment in Jira is mainly used to deduplicate
efforts by the community.
Your proposed approach to this sounds reasonable to me! Thanks!
> 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
> Priority: Minor
>
> 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)
