Hello everyone,
Well, I have a little bit more updates to the issue.
I did find that I was mistaken about pulling: nifi registry's local git does
pull from remote git repo. When I checked the nifi-registry's local git
storage, multiple ones were fully synced with remote git. However, even though
The 1 git to 1 registry doesnt really help though does it? Since you want a
production registry to always pull? You'll need to maintain 2 flows
manually (or however you do it) ?
On Mon, Jun 14, 2021 at 8:15 AM Sim, Yoosuk wrote:
> Hello everyone,
>
>
>
> Well, I have a little bit more updates to
I use DatabaseFlowPersistenceProvider, it is the simpler one. I spent some
time like you with the Git option but I gived up and chose the DB option.
It works fine. As you already require a DB for metadata, I use only one DB
for metadata and flow. Only one backup is required.
Juan
On Mon, 14 Jun 2
We use a similar approach.
We only allow our dev environment to write to the git repo (this is
controlled by using different tokens to authenticate with our git server -
one is read/write, others read-only).
We have each environment using its own branch of the git repo (e.g. dev,
staging, prod) a
Hi list,
We are trying to set a nifi secure installation using a SSL singed certificate
by our corporate CA.
This SSL certificate is signed for a domain name we'd like to use to access our
nifi server(s).
We've been unable to create a new certificate for our server using tls-toolkit
for the mai
Hey Chris, this may be a silly RTFM manual question, but I couldnt find a
way to set the branch .. now that I write this, I wonder if you use the
*?ref=BRANCH* trick
On Mon, Jun 14, 2021 at 8:30 AM Chris Sampson
wrote:
> We use a similar approach.
>
> We only allow our dev environment to write t
We use a custom start script for the pod that does a git pull and checkout
of the environment-specific branch - can't recall why but we didn't use the
Registry built-in pull mechanism (might have been branch related or
something else I've forgotten).
Cheers,
Chris Sampson
On Mon, 14 Jun 2021, 1
your deploy is that of legends .. Thanks Chris!!!
On Mon, Jun 14, 2021 at 8:47 AM Chris Sampson
wrote:
> We use a custom start script for the pod that does a git pull and checkout
> of the environment-specific branch - can't recall why but we didn't use the
> Registry built-in pull mechanism (mi
Hello everybody!
I have no experience with Amazon services but I now have to access to an API
hosted on AWS.
I have been given the following parameters:
* HTTP Method GET
* Amazon Region eu-we
Luca,
Can you check your log/nifi-app.log file for a larger error message?
Can you check your provenance data for records of the call ( that will show the
parameters etc)?
> On Jun 14, 2021, at 12:04, Luca Giovannini
> wrote:
>
>
> Hello everybody!
>
> I have no experience with Amazon
You should also confirm the resource api you are trying to call is correct.
> On Jun 14, 2021, at 12:04, Luca Giovannini
> wrote:
>
>
> Hello everybody!
>
> I have no experience with Amazon services but I now have to access to an API
> hosted on AWS.
> I have been given the following param
11 matches
Mail list logo
