Re: Isolate tenants in a multi-tenant environment

HI Adalberto, I'll respond on the users list and remove the dev list. Generally speaking, you cannot do what you are asking with Authz controls within a single NiFi cluster - but also, you probably wouldn't want to in the long run either. Even if you successfully hid tenantA from tenantB with

Re: Issue Regarding Uploading a Template using Rest-Api in Nifi-version(1.15.3)

Hi Harshit, There is a python client for NiFi, with specific support for handling templates. https://nipyapi.readthedocs.io/en/latest/nipyapi-docs/nipyapi.html#nipyapi.templates.upload_template On Tue, Oct 11, 2022, 6:11 AM harshit.varsh...@iktara.ai < harshit.varsh...@iktara.ai> wrote: > Dear

Re: NiPyAPI vs direct Python requests

I am one of the primary NiPyAPI maintainers, so my opinion is a bit biased. NiPy, by SLOC, is mostly a big library verbosely procedurally generated from the NiFi swagger spec, covering every possible command that it accepts. However, when measured by developer-hours it is primarily a pile of

Re: Accessing NIFI processors through rest api

You cannot prevent the UUIDs from changing, it is generally good practice to enforce unique names and use those as your lookup values. On Wed, 21 Apr 2021, 10:10 Vibhath Ileperuma, wrote: > Hi all, > > I'm currently developing an external script to work with a NIFI flow using > NIFI rest api.

Re: Monitoring NiFi Root Level Controller Services

Hi John, the python client nipyapi already has convenience methods in canvas.py for this, you are looking for a component status of Running. On Tue, 2 Feb 2021, 01:18 jgunvaldson, wrote: > Wiring up a rest client to make a rest request to the NIFI API, seems the > following three are possible

Re: enhancement request for NiFi variable registry support on SSLContextServices --> parameter contexts

Registry is not required to work with Parameter Contexts via the REST interface. Last time I worked with the CLI in the toolkit it did not require registry to be set up for the NiFi-specific commands to work. Working directly with the REST interface in your favourite automation language is also

Re: Updating the Concurent Tasks of a NiFi processor using Rest API

It's just update processor with that property altered, simples :) On Fri, 31 Jul 2020, 16:32 Mohit Jain, wrote: > Thanks Otto, > > That helped. > > > On Fri, Jul 31, 2020 at 4:54 PM Otto Fowler > wrote: > >> If you do it from a browser, and are using the browser debugging tools, >> you will be

Re: NIFI-API v 1.11.3 Problem when using ProcessGroupsApi.submitUpdateVariableRegistryRequest

I have had this issue in NiPyAPI when the local system does not have a timezone set, or at least setting tz_data resolved it in the docker images I was building. This was in my python client, not Java however, so I am unsure if that would affect things. On Tue, Mar 17, 2020 at 8:04 PM

Re: Best Practise Where are my FlowFiles

You can do this with NiPyAPI. Here is an example that finds all Connections with queued Flow Files, you could also look for 5min stats on processors, or process group summaries. [x for x in nipyapi.canvas.list_all_connections() if int(x.status.aggregate_snapshot.queued_count.replace(',', '')) >

Re: Regarding NiFi 1.10 parameter context

Hi Sanjeet, I am glad to hear you like NiPyAPI and have been finding it useful. I did update the client to support the new API calls for Parameters in 1.10, they are in the nipyapi.nifi.* low level client today. I plan to work on some higher level calls in nipyapi.canvas.* soon, similar to

Re: Nifi registry Kerberos Auth with Docker

Hi Tomislav, I created that build a long time ago before the official apache one was up, and it is out of date sorry. Can I suggest you switch to the official apache image that Kevin mentioned and try again? It is an up to date version and recommended by the community. On Thu, Feb 7, 2019 at 5:54

Re: Deploying versioned flows via NiFi APIs

I was recently also working through issues with non-processor components in NiPyAPI and prepared some controller service management methods. You can take a look here as it may be a shortcut to testing the automation you are looking for.

Re: Easiest way to list all NiFi processors in a release.

There is also a shortcut function NiPyApi for this, as it is handy when procedurally deploying flows: https://nipyapi.readthedocs.io/en/latest/_modules/nipyapi/canvas.html#list_all_processor_types On Mon, Nov 12, 2018 at 6:23 PM Pierre Villard wrote: > Hi Vitaly, > > Yes there is one [1]: GET

Re: upload template with REST problem

If you are looking to work with Templates programmatically, then I suggest you look at my Python client NiPyApi -https://github.com/Chaffelson/nipyapi There is a module for doing all the usual template commands:

Re: [EXT] Re: Get all Processors

Hi Karthik, I have already implemented this in NiPyApi, assuming a Python automation client is useful to you. In the nipyapi.canvas.recurse_flow command ( https://github.com/Chaffelson/nipyapi/blob/28d7f74478e5e71253ce2de53fd22f56f455c338/nipyapi/canvas.py#L36 ) is the base functionality to step

Re: Change memory limits w/ Docker image

The Dockerhub image already supports passing in environment variables to replace nifi.properties at startup, but it's a short set list. The current list is in $projRoot/nifi/nifi-docker/dockerhub/sh/start.sh It includes: # Establish baseline properties prop_replace 'nifi.web.http.port'

Re: Implementing authorization programmatically.

Building on Koji's point, there is a demo in NiPyApi for setting up a secured environment: https://github.com/Chaffelson/nipyapi/blob/master/nipyapi/demo/secure_connection.py That particular script creates a demo environment on Docker containers, but you can lift the process and underlying

Re: Progamatically clearing out flowfiles

I needed a method of manually clearing down PGs being used for automated testing of flows, so I created a purge command in the Python client. http://nipyapi.readthedocs.io/en/latest/_modules/nipyapi/canvas.html#purge_process_group There's also an option to delete a process group with purge and a

Re: NiFi Variables

Scott > > On 03/25/2018 02:50 AM, Daniel Chaffelson wrote: > > Hi Scott, > NiPyApi provides a python client for this purpose. There are calls to > get/set variables in the canvas module. > https://github.com/Chaffelson/nipyapi > > Let me know if you have any troubles

Re: NiFi Variables

Hi Scott, NiPyApi provides a python client for this purpose. There are calls to get/set variables in the canvas module. https://github.com/Chaffelson/nipyapi Let me know if you have any troubles with it. On Sun, 25 Mar 2018, 02:28 Charlie Meyer, wrote: >

Re: Error when executing NiFi REST API PUT /processors/{id} call

Hi Vitaly, To give a more detailed example of what Matt is saying, here's the Python version of what you are doing from the NiPyApi test suite. In this test we change the scheduling period of a processor to 3s: processor = nipyapi.canvas.get_processor('someprocessor') update =

Re: Reporting Specific Queue Sizes?

Hi guys, I haven't specifically built functions to wrap this, but the data is easily accessible via the API if that helps you. Let us assume for a moment that a given flow has a Processor called 'PutSyslog' for which you wish to monitor the input and output queues. This Processor receives

NiPyApi v0.8.0 released

I'm pleased to announce that NiPyApi, a Python Client SDK for Apache NiFi has a new version out. Highlights include supporting secured environments, flow versioning import/export, better templates, better documentation, more demos, and NiFi version backtesting. There are extensive release notes

Re: How to use List File/Fetch File processor in a cluster mode.

Hi Mohit, ListFile expects the directory to be on both nodes because the Primary node could swap at some point, and so the configuration has to be valid for the whole cluster. If you want to have a single directory which ListFile/FetchFile pulls from, you could try a cluster filesystem or an SFTP

Re: Registry, sdlc and promotion between environments

Hi Georg, Likewise to the toolkit CLI coming in PR2477, this functionality is targeted for NiPyApi 0.8.0 by the end of the month: https://github.com/Chaffelson/nipyapi/milestone/1 On Wed, Feb 21, 2018 at 12:37 PM Bryan Bende wrote: > Georg, > > In addition to what Joe and

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

or an advertised > address for other nodes in the cluster to use (in our case a configured > VIP) for the UI/rest api calls. Hope this makes sense. > > Cheers, > > Ryan H > > On Tue, Jan 30, 2018 at 11:54 AM, Daniel Chaffelson <chaffel...@gmail.com> > wrote: > >

Re: Updating schedule information using REST API without disturbing other processor configuration

Hi Ravi, It is not an official part of the NiFi project, but i have been collaborating with a few people on a community effort to provide Python automation for NiFi - in our next release there is functionality to reconfigure processors: Here is the relevant function in NiPyApi

Re: NiFi 1.4 Clustering Error: Cannot Replicate Request GET /nifi-api/flow/current-user

Hi Ryan, I have proposed a small change to the Docker image which may help you here - https://github.com/apache/nifi/pull/2439 Essentially it exposes the port and hostname to be used within nifi.properties as environment variables which you can pass in at runtime. Perhaps the approach used will