Re: Multiple registry instances sharing Git repo

2018-08-07 Thread Mike Thomsen
Bryan,

Thanks, that confirms what I was thinking would be the case.

Mike

On Tue, Aug 7, 2018 at 12:54 PM Andrew Grande  wrote:

> There are also registry event hooks to help with the automation.
>
> Andrew
>
>
> On Tue, Aug 7, 2018, 12:46 PM Bryan Bende  wrote:
>
>> Mike,
>>
>> It is not really made to have multiple instances pointing at the same git
>> repo.
>>
>> Each registry has a metadata DB and a flow storage component which can
>> be filesystem or git.
>>
>> So the metadata DB won't know about the stuff created in the other
>> instance.
>>
>> Generally it is either a single shared registry, or multiple
>> registries each with their own back-end storage mechanisms and then
>> you can use the CLI to promote flows between the registry instances.
>>
>> -Bryan
>>
>>
>> On Tue, Aug 7, 2018 at 12:32 PM, Mike Thomsen 
>> wrote:
>> > Has anyone tried having two or more registry instances pointing to the
>> same
>> > repo and keeping them in sync?
>> >
>> > We have a NiFi deployment where it would be an easier sell to have 3
>> > instances of the registry sharing the same repo than to have one
>> instance
>> > that is a big exception to the network security posture that separates
>> dev,
>> > test and prod environments.
>> >
>> > Any ideas on how to do this?
>> >
>> > Thanks,
>> >
>> > Mike
>>
>


Re: Multiple registry instances sharing Git repo

2018-08-07 Thread Andrew Grande
There are also registry event hooks to help with the automation.

Andrew

On Tue, Aug 7, 2018, 12:46 PM Bryan Bende  wrote:

> Mike,
>
> It is not really made to have multiple instances pointing at the same git
> repo.
>
> Each registry has a metadata DB and a flow storage component which can
> be filesystem or git.
>
> So the metadata DB won't know about the stuff created in the other
> instance.
>
> Generally it is either a single shared registry, or multiple
> registries each with their own back-end storage mechanisms and then
> you can use the CLI to promote flows between the registry instances.
>
> -Bryan
>
>
> On Tue, Aug 7, 2018 at 12:32 PM, Mike Thomsen 
> wrote:
> > Has anyone tried having two or more registry instances pointing to the
> same
> > repo and keeping them in sync?
> >
> > We have a NiFi deployment where it would be an easier sell to have 3
> > instances of the registry sharing the same repo than to have one instance
> > that is a big exception to the network security posture that separates
> dev,
> > test and prod environments.
> >
> > Any ideas on how to do this?
> >
> > Thanks,
> >
> > Mike
>


Re: Multiple registry instances sharing Git repo

2018-08-07 Thread Bryan Bende
Mike,

It is not really made to have multiple instances pointing at the same git repo.

Each registry has a metadata DB and a flow storage component which can
be filesystem or git.

So the metadata DB won't know about the stuff created in the other instance.

Generally it is either a single shared registry, or multiple
registries each with their own back-end storage mechanisms and then
you can use the CLI to promote flows between the registry instances.

-Bryan


On Tue, Aug 7, 2018 at 12:32 PM, Mike Thomsen  wrote:
> Has anyone tried having two or more registry instances pointing to the same
> repo and keeping them in sync?
>
> We have a NiFi deployment where it would be an easier sell to have 3
> instances of the registry sharing the same repo than to have one instance
> that is a big exception to the network security posture that separates dev,
> test and prod environments.
>
> Any ideas on how to do this?
>
> Thanks,
>
> Mike


Multiple registry instances sharing Git repo

2018-08-07 Thread Mike Thomsen
Has anyone tried having two or more registry instances pointing to the same
repo and keeping them in sync?

We have a NiFi deployment where it would be an easier sell to have 3
instances of the registry sharing the same repo than to have one instance
that is a big exception to the network security posture that separates dev,
test and prod environments.

Any ideas on how to do this?

Thanks,

Mike