Re: [EXT] Re: Embedded Nifi

Charlie, This was merged last week to provide an easy method to get around the host header issue with running 1.5.0 docker. Essentially it allows you to specify the host:port via environment variables. https://github.com/apache/nifi/pull/2439 On Tue, Feb 6, 2018 at 12:12 AM Charlie Meyer <

Re: [EXT] Re: Embedded Nifi

Hi Vincent, We do this for our test cases using https://github.com/palantir/docker-compose-rule. It works fairly well, but is a bit heavy weight to get tests started up locally. Also, with 1.5.0, the host header issue surfaces here and makes running in docker a pain. Hope that helps a bit! On

Re: [EXT] Re: Embedded Nifi

Perhaps Dan, but integrating docker into an automated test might prove a little challenging. I'll check it out though. Thanks, On Wed, Jan 31, 2018 at 3:00 AM, Daniel Chaffelson wrote: > Vincent, > I do something along these lines in Python to test NiFi automation work.

Re: [EXT] Re: Embedded Nifi

Vincent, I do something along these lines in Python to test NiFi automation work. NiPyApi creates the requisite Docker container(s) for the test suite, procedurally creates the NiFi/Registry objects (Process Groups, Processors, Buckets, Flows, etc), recursively tests itself, then tears itself

***UNCHECKED*** Re: [EXT] Re: Embedded Nifi

Thank you Peter. At this point I only wish to make sure that an existing flow that is already created in a flow.xml file works within an integration test. I am hoping that this can be achieved with starting Nifi programmatically this way. Thanks, On Tue, Jan 23, 2018 at 9:22 PM, Peter Wicks

RE: [EXT] Re: Embedded Nifi

Vincent, Embedded NiFi still has a long ways to go to be really useful, in my opinion; and I don't know if anyone is actively working on those improvements. The PR Andy mentioned simply allows you to startup NiFi inside your process instead of running it directly from a startup script, but