Hi Team, I was touching some test related code in the other day and it brought to my attention how much partly duplicated nifi.properties files we do have in the project in various places.
While I was searching for the value of a given property in these files, it got me thinking that when a property is changing (for example related to the 2.x efforts) or added, it indicates changes in multiple places, which could lead to oversights and inconsistencies. Additionally, it seems to me that duplicating whole configuration files might make one reluctant to create specific properties files for specific tests like in case of the system tests. I would like to propose a discussion about this, being curious if the community sees any value in improving the configuration management. My initial thoughts is to maintain one single “source of truth” properties file and providing some kind of utility, which could generate instances as needed allowing to override or extend properties when necessary. Looking forward to your insights and suggestions. Regards, Bence
