I'm wondering if there's any established best practices for the deployment of templates, particularly in contexts where a NiFi Registry instance cannot be used as the environments are isolated in such a way that they would not be able to access a centralised registry.
Each environment has its own unique properties, so the properties for various NiFi components (processors, controller services...) will be set to values unique to that environment.
This is complicated by sensitive properties and properties that don't support the expression language (which enables the use of variables). For example, during development time of a NiFi flow, the properties that don't support EL require the use of static values that aren't applicable to other environments.
This seems to require a mapping of NiFi properties to environment configuration. i.e. if we have a a processor of type "foo" then the processor property called "Username" should map to the environment configuration "baz".
The above was originally posted in the Community Help Track. On Tue Jun 4 01:52 UTC 2019, a member of the HCC moderation staff moved it to the Data Ingestion & Streaming track. The Community Help Track is intended for questions about using the HCC site itself.
Bill Brooks, Community Moderator Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.