Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to pull the github repository automatically? #24

Open
joselmh opened this issue Jul 20, 2021 · 0 comments
Open

How to pull the github repository automatically? #24

joselmh opened this issue Jul 20, 2021 · 0 comments

Comments

@joselmh
Copy link

joselmh commented Jul 20, 2021

I have two different instances of Nifi Registry running. One in a dev environment and the other one in a prod environment. Both pointing to the same github repository and running on a Azure Kubernetes cluster.
When I commit my changes in a process group from dev env, a new version is created. The change is pushed and I can see it in the github repo. But the pro instance is never aware of that change, so I'm no able to upgrade that process group with the new version. Even by running a git pull in the prod container shell. When I do that I see the log of the pull, the change is there, but Nifi doesn't notice it.
Only when I restart the prod instance of Nifi Registry I am able to see that there is another available version of that process group and upgrade it.
Is there any way to automatize it so, both registry instances are always synchronized?

The version of the docker image I'm using is nifi-registry:0.8.0-default

thank you very much in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant