Julien Guitton

I ask this without having tested it, but won't these parameters be considered as changes in the versioning of the dataflows and cause repeated rollbacks of them?

> Was this logback.xml just copied from the 2.0.0-M1 baseline? Yes directly copied from the docker image.

> We should also update the `nifi-cluster` helm chart logback.xml since it routes all of the appender output to the Console (stdout). It's verbatim copied and it includes an additional...

> Do you think there's any risk in merging this for nifikop 1.x? I discussed with @erdrix yesterday about the suppression of the file. And he said that we shouldn't....

> > > Do you think there's any risk in merging this for nifikop 1.x? > > > > > > I discussed with @erdrix yesterday about the suppression of...

> > After further investigations with the help of @juldrixx we are not sure that the option `nifi.security.autoreload.enabled` is enough to apply new certificates. If any of you has an...

I have recreated the problem. I set a `Duration` of 1h and a `RenewBefore` of 5m, so the certificates expire after 1h. When the certificates have expired, the user interface...

> > > > After further investigations with the help of @juldrixx we are not sure that the option `nifi.security.autoreload.enabled` is enough to apply new certificates. If any of you...

I've talked to the folks at NiFi and @michael81877, and it doesn't seem like this is expected behavior ([link to discussion](https://apachenifi.slack.com/archives/CDGMCSDJT/p1662035605327149)). I have opened [a ticket](https://issues.apache.org/jira/browse/NIFI-10425) at NiFi to have...

> Is it worth looking at replacing the `nifi.properties` logic we have here, to make use of the ENV scripts in `apache/nifi`'s docker image instead? My worry with using templates...