Dan Chaffelson

I would call the schedule_controller operation, and then run a loop fetching the component and printing it every second, specifically looking at the component.state. The state should be a string,...

I suspect you are right @ottobackwards - possibly we should add a check in the mustache templates that we are getting the expected object and not a plain String, as...

``` nipyapi.nifi.apis.processors_api.ProcessorsApi( api_client=nipyapi.config.nifi_config.api_client).update_run_status( id=processor_id, body=nipyapi.nifi.models.ProcessorRunStatusEntity( revision=nipyapi.nifi.models.RevisionDTO( version=processor_version ), state='RUN_ONCE' ) ) ) ``` I would expect this to work. You are correct that update_run_status is a separate call to update_processor...

Hmm, that is interesting. So if you PUT a RUN_ONCE in an update_run_status, and then immediately GET the processor again it can error because of the validation? I should be...

Hi @marcelo225 - NiPy is currently built on the NiFi-1.27 API spec, and while that has some forward compatibility with the 2.x API spec, I haven't yet had the time...

Apologies I should've updated this with the NiPyAPI 1.0 release - this should be resolved now if you move to ver1, as it supports NiFi v2.x, including the new git*...

Superceded by https://github.com/Chaffelson/nipyapi/pull/365

In the linked ticket, the user uses the set_ssl_context call, rather than updating the default context. Possibly there is some mismatch between the behaviours of the default vs. explicit functions...

Closing as no further action requested, please reopen if this still needs addressing.

Hi Chris - where are you reading them at the moment, on https://nipyapi.readthedocs.io/en/latest/ ? So I can better understand the ask, can you give me a quick run through of...