Dan Chaffelson

You are correct, the current NiPyAPI high-level calls do not handle Reporting Tasks. Your best option here would be to create the task in the GUI, and record the calls...

I don't think this is actually NiPyAPI itself, but one of the dependencies - or at least, I cannot see where we import cryptography.utils directly in the project, it is...

I agree this could be a useful enhancement. You will need to handle Controllers, and also as you say check for hung threads and coerce them to stop if you...

Interesting requirement @colinfindlay-nz I can see a potential pathway recursing through the exported flow seeking the references and fetching/integrating them into the exported json. I'd think I'd just have to...

Ok I think I can work up a limited contrived demo - there's edge cases we can't handle, like nested PGs coming from different registries that may not be available...

Nested PGs generally aren't supported anyway, and don't work well in registry. The error you received says that you need to check the NiFi log as the server was unable...

Controllers are imported if attached to the versioned PG. Parameter contexts are not importable in that way, you must recreate them via the GUI or API. The standard design is...

Don't use nested PGs, or only version the top most one. On Tue, 11 Aug 2020, 09:22 charu123409, wrote: > One more doubt, it won't even work from one bucket...

Did you try disabling SSL verification in config.py? On Tue, 13 Oct 2020, 11:55 error0x1, wrote: > > - Nipyapi version: last > - NiFi version: 1.9.0 > - NiFi-Registry...

Right, I think you're hitting a bug I've recently been nailing down with authentication and authorization (always fun to debug). From speaking to other members of the NiFi community I...