Manish, Maybe not available as a variable necessarily (this will come later), but you can apply properties when you deploy your template. Basically, set them directly as part of the deployment. Take a look https://github.com/aperepel/nifi-api-deploy
Andrew From: Manish Gupta 8 <mgupt...@sapient.com<mailto:mgupt...@sapient.com>> Reply-To: "users@nifi.apache.org<mailto:users@nifi.apache.org>" <users@nifi.apache.org<mailto:users@nifi.apache.org>> Date: Thursday, April 28, 2016 at 3:08 AM To: "users@nifi.apache.org<mailto:users@nifi.apache.org>" <users@nifi.apache.org<mailto:users@nifi.apache.org>> Subject: NiFi - Configuration option Hi, What is the best option for storing root/processor group level configurations? From “Expression Language Guide”, I know one can use environment variable or JVM system property. Or specify the value for one flow using an update attribute processor near the top of the flow. But is there a way I can have a single property / xml file to have my all the configurations available and each property be available in nifi as a variable? Thanks, Manish
