Github user colindean commented on the issue:
https://github.com/apache/nifi/pull/3133
> What about making all of the new fields not required? `required(false)`.
Then, if a value is provided, you override, otherwise you leave it be. You
could call out the default values, or default functionality at least, in the
property description?
I _could_ go this route, but I'm not where to strike the balance between
"explicit settings from defaults at the time of creation" versus "use the
latest default". I could reference the DBCP default constants in the property
description, too, thus preventing the description from becoming out of dateâ¦
---
