There is no automatic pulling from git. The way registry works is that
there is a database (H2/MySql/Postgres) that stores all the metadata
and knowledge of what items exist, and then a persistence provider for
each time of versioned item (flows, extension bundles). Git is just an
implementation of
Hi Chris, Bryan,
Thanks for the answers.
How to configure "follower" Registries to pull from the "leader" automatically?
What if one of the Registries goes down, how to recover, is it tricky?
We have three separated envs, with separated nifi registries. Is it even
required to have git as a per
It wasn't really meant for that, but as others pointed out, if only
one of the registries is doing writes and the others are read-only for
pulling into nifi in another environment, then it can work.
The best option is to have one central registry that all nifi's can
access (if you are willing to a
Yes -- however:
- only one should be the authority
- see the older thread of how you need to have the read-only-clients
re-poll the remote git in order ot pick up the latest changes.
On Wed, Jun 23, 2021 at 5:25 AM Tomislav Novosel <
tomislav.novo...@clearpeaks.com> wrote:
> Hi to all,
>
>
>
> i
Hi to all,
i sit possible to have one central Git repo for multiple NiFi registries
as persistance layer?
Ii it possible to configure, for example, three NiFi registries (through
providers.xml file)
to communicate with one git repo?
Thanks,
Tom
