Hello, Just wanted to add that it is probably still good practice to back up the database, or use an external highly available DB.
As we build out the registry we will be storing more information in the database, and not all of it will come from git, so at some point the entire database may not be able to be rebuilt from just git. Although just for flows it should be fine. Thanks, Bryan On Thu, Jan 31, 2019 at 7:18 PM Pierre Villard <[email protected]> wrote: > Hi Elemir, > > I think you're looking for NIFIREG-209 [1] to be released in the next > version of the NiFi Registry. > > [1] https://issues.apache.org/jira/browse/NIFIREG-209 > > Pierre > > Le ven. 1 févr. 2019 à 00:46, Elemir Stevko <[email protected]> > a écrit : > >> Hello, >> >> >> >> In NiFi Registry configured with Git provider, is it possible to import >> the content of an existing Git repo in a new NiFi instance? >> >> >> >> To provide some context, I am working on automating NiFi Registry server >> instantiation in AWS. I am planning to store the versioned flows in Git >> (CodeCommit) and I am considering the best way to backup and restore the >> state of NiFi Registry server to recover from failure. >> >> >> >> NiFi Registry creates a data structure in the local database (H2) >> describing the available buckets and flows. I am wondering if the content >> of the Git repository is enough to preserve the state or if I need to >> backup the database too (or perhaps externalise it as a Postgres RDS >> instance). My tests so far indicate that it's the latter, but I want to >> confirm that this is correct. >> >> >> >> Best regards, >> >> Elemir >> >> >> > -- Sent from Gmail Mobile
