Hi Marcus, Parameters and Contexts are the replacements for Variables and the variable registry files. Support for the latter is gone in NiFi 2.0.
Parameters Contexts are meant as the permanent storage for both normal and sensitive parameters, but there are some new features getting them from external storage (like Azure Keyvaults if those apply). You'll need a much newer version of NiFi for that though. NiFi 1.28 has been released this week, in fact. With a newer NiFi and Registry, you can commit flows and deploy them in another environment while the parameter contexts stay in their own environment. This is very convenient compared to maintaining a bunch of external files. The first time you deploy a flow that uses a new Parameter Context, it'll get imported to the new environment and you can then enter the correct values. After that, the existing values for that environment are not touched anymore. Hope this helps, Isha Van: Ling, Marcus <[email protected]> Verzonden: vrijdag 1 november 2024 16:35 Aan: '[email protected]' <[email protected]> Onderwerp: NIFI - Using externalised variables to set SSL Context attributes. You don't often get email from [email protected]<mailto:[email protected]>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi, I've been away from NIFI for a couple of years, and trying to regather my thoughts on how to do various things. I'm trying to set up a Standard SSL Context using externalised variables from the nifi.varaible.registry.properties file. The fie contains variables for keystores, truststores and their passwords. I can see that in in order to set the properties in the Standard SSL Context service, the values must be parameters not variables. I have set a context for the progress group in question, and assigned parameters that 'point' to the external variables in the variables file. Eg: #{aaa} = ${a value in the variables file} But it says that the file (in this case) is not readable. (it is if I hard code the values) I assume I'm missing something somewhere but unsure ow if I am doing the right thing. Also I'm trying to do this for the passwords, which obviously are sensitive fields, and unsure I can externalise them anyway? NIFI version = 1.12.1 NIFI registry = 0.3.0 (Don't ask!!) Any thoughts? Thanks Marcus Marcus R Ling BAE Systems Digital Intelligence ___________________________________________________________ T: +44 (0) 1452 635083 | E: [email protected]<mailto:[email protected]> BAE Systems Digital Intelligence, 1120 The Square Gloucester Business Park, GL3 4AD www.baesystems.com/digital<http://www.baesystems.com/digital> BAE Systems will collect and process information about you that may be subject to data protection laws. For more information about how we use and disclose your personal information, how we protect your information, our legal basis to use your information, your rights and who you can contact, please refer to the relevant sections of our Privacy note at www.baesystems.com/en/cybersecurity/privacy<http://www.baesystems.com/en/cybersecurity/privacy> Please consider the environment before printing this email. This message should be regarded as confidential. If you have received this email in error please notify the sender and destroy it immediately. Statements of intent shall only become binding when confirmed in hard copy by an authorised signatory. The contents of this email may relate to dealings with other companies under the control of BAE Systems PLC, details of which can be found at http://www.baesystems.com/Businesses/index.htm.
