Have a look under Flow in the API. There you'll find GET /flow/parameters-contexts to retrieve a list.
On Mon, Dec 2, 2019 at 4:48 PM Bahlul Haider <[email protected]> wrote: > Friendly Monday ping. > > Thanks, > Bahlul > > On Wed, Nov 27, 2019 at 10:29 AM Bahlul Haider <[email protected]> > wrote: > >> Thank you Mark for your for your reply. >> >> According to the NIFI API documentation >> <http://nifi.apache.org/docs.html>, parameter-contexts is for creating >> a new parameter context. >> [image: image.png] >> Yesterday, I blindly tried different "ParameterContextEntry" in the API >> but failed to list all the parameter contexts. It can only create a new >> Parameter Context and returns json with ID of the newly created parameter >> context. >> >> Thanks, >> Bahlul >> >> >> On Wed, Nov 27, 2019 at 5:39 AM Mark Bean <[email protected]> wrote: >> >>> The /parameter-contexts endpoint will give you all the parameter contexts >>> which you have permission to access. You will have to parse the JSON to >>> find the name and/or ID. >>> >>> -Mark >>> >>> On Tue, Nov 26, 2019 at 2:54 PM Bahlul Haider <[email protected]> >>> wrote: >>> >>> > I was able to use the API's to create parameter context. >>> > >>> > Currently my parameter context is stored in the registry (except the >>> secret >>> > values). Every time I create a new nifi cluster from the registry, the >>> > parameter context gets a different ID. To be able to add the secrets >>> using >>> > nifi-api I need to know the ID of the parameter context. However, it >>> looks >>> > like there is no api to get an ID from parameter context name. Did I >>> miss >>> > something or is there any undocumented APIs list all parameter >>> contexts? >>> > >>> > Thanks, >>> > Bahlul >>> > >>> > On Mon, Nov 25, 2019 at 11:10 AM Bahlul Haider <[email protected] >>> > >>> > wrote: >>> > >>> > > Thank you Mark for your quick reply. This is what I was looking for >>> but >>> > > was unable to find it. >>> > > >>> > > I will see if I can create the parameter context using the REST APIs. >>> > > >>> > > Thanks, >>> > > Bahlul >>> > > >>> > > On Mon, Nov 25, 2019 at 10:49 AM Mark Bean <[email protected]> >>> > wrote: >>> > > >>> > >> Bahlul, >>> > >> >>> > >> You can access parameter contexts via the NiFi REST API. See >>> > >> /parameter-contexts under the Controller in the API documentation. >>> > >> >>> > >> http://nifi.apache.org/docs.html >>> > >> >>> > >> -Mark >>> > >> >>> > >> On Mon, Nov 25, 2019 at 1:12 PM Bahlul Haider < >>> [email protected]> >>> > >> wrote: >>> > >> >>> > >> > Friendly Monday morning ping. >>> > >> > >>> > >> > I am looking for a way to programmatically setting/updating >>> parameters >>> > >> in >>> > >> > newly created nifi cluster. >>> > >> > >>> > >> > Thanks, >>> > >> > Bahlul >>> > >> > >>> > >> > On Fri, Nov 22, 2019 at 1:28 PM Bahlul Haider < >>> [email protected] >>> > > >>> > >> > wrote: >>> > >> > >>> > >> > > Hey Bryan, >>> > >> > > >>> > >> > > I was able to manually add parameters in a flow and was able to >>> use >>> > >> them. >>> > >> > > However I did not find a way to programmatically create the >>> > parameter >>> > >> > > context values in new nifi cluster. Any help regarding this is >>> > greatly >>> > >> > > appreciated. >>> > >> > > >>> > >> > > Happy Friday :-) >>> > >> > > >>> > >> > > Thanks, >>> > >> > > Bahlul >>> > >> > > >>> > >> > > On Thu, Nov 21, 2019 at 4:57 PM Bahlul Haider < >>> > [email protected] >>> > >> > >>> > >> > > wrote: >>> > >> > > >>> > >> > >> Thank you very much Bryan for your quick reply. >>> > >> > >> >>> > >> > >> I actually started with 1.10.0. But when I tried to pass >>> variables >>> > to >>> > >> > the >>> > >> > >> flow using nifi CLI I was getting an error (see my comments in >>> NIFI >>> > >> > >> 6814: Nifi REST api returns incompatible date format for NiFi >>> > Client >>> > >> DTO >>> > >> > >> < >>> > >> > >>> > >> >>> > >>> https://issues.apache.org/jira/projects/NIFI/issues/NIFI-6860?filter=allopenissues >>> > >> > >). >>> > >> > >> The regression was later fixed. >>> > >> > >> >>> > >> > >> I will try parameters in 1.10. >>> > >> > >> >>> > >> > >> Thanks, >>> > >> > >> Bahlul >>> > >> > >> >>> > >> > >> On Thu, Nov 21, 2019 at 11:10 AM Bryan Bende <[email protected] >>> > >>> > >> wrote: >>> > >> > >> >>> > >> > >>> Hello, >>> > >> > >>> >>> > >> > >>> If you can use the latest 1.10.0 release there is a new >>> feature >>> > >> called >>> > >> > >>> parameters that will greatly help with this. >>> > >> > >>> >>> > >> > >>> You can use a new syntax #{my.secret} which will remain in the >>> > flow >>> > >> > >>> when saved to registry. >>> > >> > >>> >>> > >> > >>> Then you can use CLI commands for setting the value of the >>> > parameter >>> > >> > >>> named "my.secret". >>> > >> > >>> >>> > >> > >>> Thanks, >>> > >> > >>> >>> > >> > >>> Bryan >>> > >> > >>> >>> > >> > >>> On Thu, Nov 21, 2019 at 2:04 PM Bahlul Haider < >>> > >> [email protected]> >>> > >> > >>> wrote: >>> > >> > >>> > >>> > >> > >>> > Hello, >>> > >> > >>> > >>> > >> > >>> > I am working on automatically starting a flow from registry >>> in >>> > >> newly >>> > >> > >>> > created nfi clusters. To start the flow, I need to provide >>> some >>> > >> > secret >>> > >> > >>> > values to some of the processors. What is the recommended >>> way of >>> > >> > >>> > programmatically provide secret of a processor? >>> > >> > >>> > >>> > >> > >>> > So far, I have tried NiFi CLI to pass secrets as variables >>> to >>> > NiFi >>> > >> > >>> (e.g., >>> > >> > >>> > {secretName, secretValue}) and reference ${secretName} in >>> the >>> > >> > >>> processor (I >>> > >> > >>> > am aware that NiFi does yet support encryption for secrets >>> in >>> > >> > >>> variables). >>> > >> > >>> > However, I am unable to create a new version of the flow >>> (from >>> > the >>> > >> > >>> browser) >>> > >> > >>> > in the registry with ${secretName} as the property value >>> (NiFi >>> > >> thinks >>> > >> > >>> it is >>> > >> > >>> > a secret and does not include it in the new version). I was >>> > hoping >>> > >> > that >>> > >> > >>> > NiFi CLI have a way to update flow in registry with >>> > ${secretName} >>> > >> as >>> > >> > >>> secret >>> > >> > >>> > value. However, I did not find a way to to do it. >>> > >> > >>> > >>> > >> > >>> > I am a newbie to nifi. Any help regarding this is greatly >>> > >> > appreciated. >>> > >> > >>> I >>> > >> > >>> > have seen there are several similar open issues in nifi. I >>> am >>> > >> willing >>> > >> > >>> to >>> > >> > >>> > work on those issues if my scenario is not supported. >>> > >> > >>> > >>> > >> > >>> > Thanks, >>> > >> > >>> > Bahlul >>> > >> > >>> >>> > >> > >> >>> > >> > >> >>> > >> > >> -- >>> > >> > >> Thanks, >>> > >> > >> Bahlul >>> > >> > >> >>> > >> > >> >>> > >> > > >>> > >> > > -- >>> > >> > > Thanks, >>> > >> > > Bahlul >>> > >> > > >>> > >> > > >>> > >> > >>> > >> > -- >>> > >> > Thanks, >>> > >> > Bahlul >>> > >> > >>> > >> >>> > > >>> > > >>> > > -- >>> > > Thanks, >>> > > Bahlul >>> > > >>> > > >>> > >>> > -- >>> > Thanks, >>> > Bahlul >>> > >>> >> >> >> -- >> Thanks, >> Bahlul >> >> > > -- > Thanks, > Bahlul > >
