Wouldn’t it be like the proxy configuration and the aws configuration stuff ( optional )? Is there any kind of ‘property’ depreciation plan?
If you say make it optional for a little while, that doesn’t mitigate issues in the future when it is *not* optional. On June 15, 2018 at 08:12:05, Mike Thomsen ([email protected]) wrote: I created a ticket for moving the Mongo processors to use the Mongo client service as their configuration source. https://issues.apache.org/jira/browse/NIFI-5239 For at least one release, it should be optional, but I'm not sure the best way to do that. Should I make the client service and the required configuration fields optional and use customValidate to verify that one or the other are set properly? Thanks, Mike
