Great idea Yolanda!
Andre,
Aldrin and I discussed something similar in the comments of NIFI-2974 last year
but didn’t follow up on it. I think you’ve gotten sufficient support here to
file a Jira and scope it out. I know as someone who is constantly rebuilding
and redeploying the application, I have shortcuts to c
👍
Mit freundlichen Grüßen / best regards
Kay-Uwe Moosheimer
> Am 25.04.2017 um 18:16 schrieb Yolanda Davis :
>
> Hi Andre,
>
> Just wanted to add my thoughts on this. One of the things I have been
> thinking and working through in creating utilities to automate upgrades
> (see https://issues.a
Hi Andre,
Realized I responded on the wrong thread...
Just wanted to add my thoughts on this. One of the things I have been
thinking and working through in creating utilities to automate upgrades
(see https://issues.apache.org/jira/browse/NIFI-3663) is creating the
ability to migrate to new conf
Hi Andre,
Just wanted to add my thoughts on this. One of the things I have been
thinking and working through in creating utilities to automate upgrades
(see https://issues.apache.org/jira/browse/NIFI-3663) is creating the
ability to migrate to new configurations/settings, especially in the
instan
This is a great idea!
Mit freundlichen Grüßen / best regards
Kay-Uwe Moosheimer
> Am 25.04.2017 um 17:03 schrieb Andre F de Miranda :
>
> dev,
>
> What do you think about the idea of allowing an user to configure overrides
> for the "master" configuration files in order to smooth upgrades?
>
>
I think this is a great idea. It would also provide a standard integration
point for the tls-toolkit command and similar utilities.
On Tue, Apr 25, 2017 at 8:03 AM, Andre F de Miranda wrote:
> dev,
>
> What do you think about the idea of allowing an user to configure overrides
> for the "maste
dev,
What do you think about the idea of allowing an user to configure overrides
for the "master" configuration files in order to smooth upgrades?
In my opinion candidates would be_ bootstrap.conf_ and _nifi.properties_
as they contain the links to all other files (logback.xml excluded).
Upon
dev,
What do you think about the idea of allowing an user to configure overrides
for the "master" configuration files in order to smooth upgrades?
In my opinion candidates would be_ bootstrap.conf_ and _nifi.properties_
as they contain the links to all other files (logback.xml excluded).
Upon
