Often there are strictly separate environments: Test environment Production environment
Let's assume we have 10+ flow templates which describes different processes. Each of them contain connections to database, connections to JMS broker and to remote servers. A test environment should be as close to production as possible. Often it is not allowed to do any testing in production environment. This means that templates should be exactly same for test and production environments. Only database, JMS broker and remote servers are different. It would be extremely helpful to have some kind of named resources. For example template contains only reference to named resource DATABASE. When we use template in test environment, DATABASE will be mapped to test database. And when we move template to production environment, template will use live database instead. This way we can easily test, modify and deploy without changing configuration in each template when switching between test and live. And not to worry possible little mistakes and differences in configuration. Thanks toivo -- View this message in context: http://apache-nifi-incubating-developer-list.39713.n7.nabble.com/Great-question-on-nifi-IRC-room-today-NiFi-BPM-sharing-configuration-tp787p799.html Sent from the Apache NiFi (incubating) Developer List mailing list archive at Nabble.com.
