You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Rabi Kumar K C (Jira)" <ji...@apache.org> on 2019/11/16 20:55:00 UTC

[jira] [Assigned] (NIFIREG-227) GitFlowPersistenceProvider option to clone repo on startup

     [ https://issues.apache.org/jira/browse/NIFIREG-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rabi Kumar K C reassigned NIFIREG-227:
--------------------------------------

    Assignee: Rabi Kumar K C

> 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
>
> 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)