Closed jamesduffy closed 5 years ago
Hi @jamesduffy The architecture of the library is to connect to one environment at a time, but switch between environments as requirements dictate, which may be done within the same script.
For an example of how this works, you can look at the FDLC demo within the library, which creates two Docker environments (Dev & Prod) and procedurally creates and version controls flows between them. I suggest running the demo, and examining the script while you execute it to understand the usages of the various functions.
Let me know how you get on.
Hi @jamesduffy - as @Chaffelson says the FDLC demo switches between environments e.g.
nipyapi.utils.set_endpoint(prod_nifi_api_url)
documented here
No further comments in a month. Please reopen if you need more advice :)
Description
I want to connect to different NiFi servers within the same script. I currently have a loop, but when looking at the data returned it is data from the first set server and not the other server. I have tried reloading the module each time. It would probably be easier to initialize a class instead of configuring a module. I would prefer to do something like the following:
What I Did
Urgency
We are unable to use this library because we need to connect to multiple NiFi server/clusters from within the same script.