Dan Chaffelson

I have started to investigate this. It will require additional test harness to support properly, as I will need to test connecting between two separate NiFi instances and validating that...

@hamzabekkouri my apologies this has been sitting here for so long, is it now resolved or do you need some assistance? I will be around this week.

The short answer here is that the canvas calls are for Controllers at the canvas level, which are accessed in the GUI via the cog icon within a progress group...

This makes good sense, if you want to go ahead and implement that would be great. Sorry I hadn't seen this until now, not sure what has happened to my...

Really interesting situation to look into and resolve, I think @kevdoran might also be interested.

You'll want to look in nipyapi.nifi.configuration, nipyapi.registry.configuration, and the root nipyapi.config. Each defines the logging handlers associated, though with the root one it just does a basic config by default....

I am unsure why you aren't using canvas.list_all_controllers and filtering to the controller you need here? You may also want to use nipyapi.utils.set_endpoint to connect to the NiFi environment.

Bindings may also have Conditions, which would be too complex to implement without a separate module. I would quite like to see this done as well, so I don't have...

This collection is effectively abandoned and is being removed from the main Ansible family, see [here](https://github.com/ansible-community/community-topics/issues/105) for details. The problem would be that PRs are not being reviewed and merged...

@WillDyson @hcoyote would this only be changed in CDH7, and possibly still be required for older versions?