Re: Nifi Registry GitFlowPersistenceProvider

t;> >>>> >>>> The only way to resolve it yet was to do something similar to >>>> Hesselmann’s method: we dropped the metadata backend database in postgresql >>>> and redeploy nifi-registry to repopulate the metadata. This worked, but it >>>> certainly does

Re: Nifi Registry GitFlowPersistenceProvider

t; >>> >>> >>> At the moment, I am more inclined to give one git dedicated to one nifi >>> registry, unless I can find a simpler way to handle nifi-registry sync >>> issue. >>> >>> >>> >>> Any suggestions? >>&

Re: Nifi Registry GitFlowPersistenceProvider

complications in the development process. >> >> >> >> At the moment, I am more inclined to give one git dedicated to one nifi >> registry, unless I can find a simpler way to handle nifi-registry sync >> issue. >> >> >> >> Any suggestions? >

Re: Nifi Registry GitFlowPersistenceProvider

t dedicated to one nifi > registry, unless I can find a simpler way to handle nifi-registry sync > issue. > > > > Any suggestions? > > > > Cheers, > > > > Tony Sim > > > > *From:* Hesselmann, Brian > *Sent:* June-07-21 3:58 PM > *To:* users

Re: Nifi Registry GitFlowPersistenceProvider

;> >> >> Any suggestions? >> >> >> >> Cheers, >> >> >> >> Tony Sim >> >> >> >> *From:* Hesselmann, Brian >> *Sent:* June-07-21 3:58 PM >> *To:* users@nifi.apache.org >> *Subject:* [EXT]Re: Nifi Re

Re: Nifi Registry GitFlowPersistenceProvider

one git dedicated to one nifi > registry, unless I can find a simpler way to handle nifi-registry sync > issue. > > > > Any suggestions? > > > > Cheers, > > > > Tony Sim > > > > *From:* Hesselmann, Brian > *Sent:* June-07-21 3:58 PM >

RE: Nifi Registry GitFlowPersistenceProvider

egistry, unless I can find a simpler way to handle nifi-registry sync issue. Any suggestions? Cheers, Tony Sim From: Hesselmann, Brian Sent: June-07-21 3:58 PM To: users@nifi.apache.org Subject: [EXT]Re: Nifi Registry GitFlowPersistenceProvider The easiest way I found to sync nifi registry

Re: Nifi Registry GitFlowPersistenceProvider

istry. Van: Chris McKeever Verzonden: maandag 7 juni 2021 16:49:21 Aan: users@nifi.apache.org Onderwerp: Re: Nifi Registry GitFlowPersistenceProvider EXTERNAL SENDER: Do not click any links or open any attachments unless you trust the sender and know the content is safe. EXPÉDITEUR EXTERN

Re: Nifi Registry GitFlowPersistenceProvider

Tony - did you ever get an answer on this? On Fri, Jun 4, 2021 at 9:04 AM Chris McKeever wrote: > oooh, this is interesting ... I know only one registry could/should be the > authoritative WRITER .. > maybe there is a fetch hook that you can schedule to refresh ... following > > On Fri, Jun 4, 2

Nifi Registry GitFlowPersistenceProvider

Hello everyone, I am currently setting up Nifi Registry. In our setup, we wanted multiple Nifi Registry to talk to the same remote git repository. (say, one in DEV, and another in QA, etc.) Over time, I found that not all Nifi Registry retained the same information, even though the remote git